Yes, UNIX domain sockets use the file system as the address name space, .i.e. the file path instead of URL/IP and port. The man page for socket says
Socket creates an Internet domain TCP or a UNIX domain stream
socket and connects it to stdin and stdout. The host argument can
be an Internet number in dot-notation (like ``130.149.28.10'') or
a domain name. In this case it must be possible to resolve the name to
a valid Internet address with gethostbyname. The port
argument can be a port number or a service name which can be mapped to
a port number by getservbyname. If an UNIX domain socket is
wanted to be created instead of an Internet socket, specify the path
instead of an internet (canonical domain named or dot-notated) host.
The hostname is treated as a pathname if contains at least a single
slash. I.e. if one wants to create or connect to a socket in the
current directory, use ./filename to specify the connection point.
Unix domain sockets are faster than IP Sockets for local interprocess communication, see here and here or this related question.
man socket
many people aren't aware the manual covers more than just commands.