Skip to main content
Every conversation of a deployed agent is reachable at one address:
The host is the Edge Compute function’s public URL. The path is the mount’s. The shape of the request selects the transport, not the path: The upgrade reaches the instance’s webSocket(ws, req) entry. The GET and the POST reach its fetch(req) entry. The AgentClient 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 runs inside the instance. Mounting Agents is the reference, and its authorization section covers both gates.
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 has the detail.