> ## 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.

# Virtual Private Cloud

> Agents reach services inside the user's network through an Agent Gateway.

> [!WARNING]
>
> **Preview.** Not available yet.

An agent on the user's [*Network*](https://developers.telnyx.com/docs/network/overview.md) reaches services inside the user's network, such as MCP servers and APIs, through an Agent Gateway instance. No service needs a public address. These are the pieces that build it:

| Artifact | What It Does | Where |
| - | - | - |
| [*Network*](https://developers.telnyx.com/docs/network/overview.md) | Holds the instance, the agents, and the routes to the user's network. | Telnyx |
| [WireGuard Interface](https://developers.telnyx.com/docs/network/wireguard-interfaces.md) | Attaches the instance and the agents to the *Network*. | Telnyx |
| [Agent Gateway instance](https://developers.telnyx.com/docs/agent-gateway/quick-start.md#create-the-agent-gateway) | Takes every request from the agents at its `gateway_url`, and reaches the services for them. | Telnyx |
| [Edge Compute function](https://developers.telnyx.com/docs/edge-compute/overview.md) with a [network binding](https://developers.telnyx.com/docs/edge-compute/runtime/bindings/network.md) | Runs an agent on the *Network*, public or private. | Telnyx |
| [Route](https://developers.telnyx.com/docs/network/routes.md) | Sends a CIDR of the user's network to a forwarding peer or to a tunnel. | Telnyx |
| Forwarding peer, a [WireGuard peer](https://developers.telnyx.com/docs/network/wireguard-interfaces/quick-start.md) | Forwards traffic from the *Network* to the subnets behind it. | The user's network |
| Tunnel hosts, running a [Tunnel](https://developers.telnyx.com/docs/network/tunnel.md) | Connect out to Telnyx, with no change to the user's router or firewall, and carry traffic to the subnets they reach. | The user's network |

A forwarding peer and tunnel hosts are two ways into the same subnets. Either one carries the instance's requests to the services.