> ## Documentation Index
> Fetch the complete documentation index at: https://developers.telnyx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# The Address and Transports

Every conversation of a deployed agent is reachable at one address:

```text theme={null}
https://<name>-<func-id-prefix>.telnyxcompute.com/agents/<name>/<conversation>
```

The host is the Edge Compute function's [public URL](/docs/edge-compute/configuration/routing#public-url-pattern). The path is the mount's.

The shape of the request selects the transport, not the path:

| The client sends | It gets | Use |
| - | - | - |
| `Upgrade: websocket` | The agent socket protocol: state and message sync, cursor-based resume | Clients, and the voice media stream |
| `GET …?subscribe=state` | Server-Sent Events | State and message streams in a browser |
| `POST …/rpc/<method>` | One RPC call, JSON in and out | Any HTTP client |

The upgrade reaches the instance's [`webSocket(ws, req)`](/docs/edge-compute/stateful-actors/api-reference/base#websocket-ws-req) entry. The `GET` and the `POST` reach its [`fetch(req)`](/docs/edge-compute/stateful-actors/api-reference/base#fetch-req) entry.

The [AgentClient](/docs/agent-sdk/client-sdk/constructor) wraps the socket, and any HTTP or WebSocket client can speak the wire. The mount routes and adds no policy of its own. Two gates decide who may call. The mount's `authorize` runs at the edge, and the agent's [`authorize`](/docs/agent-sdk/interface/authorize) runs inside the instance. [Mounting Agents](/docs/agent-sdk/mounting-agents) is the reference, and its [authorization section](/docs/agent-sdk/mounting-agents#authorization-composes-—-it-does-not-replace) covers both gates.

> [!WARNING]
>
> **Beta.** On a deployed function, Server-Sent Events arrive in batches about once a second rather than live. The WebSocket carries the same frames on the same address and is the live path. [AgentHttpServer](/docs/agent-sdk/internals/the-http-server) has the detail.