Telnyx network globe: colocated GPUs, privately owned fiber between PoPs, and direct PSTN interconnects.

Infrastructure for realtime agents

The network that makes realtime agents real

The carrier license, the fiber, the PoPs, the GPUs. One network, end to end. Nothing you build here transits a hop we don't operate.

Explore our network

Points of presence
25+
Carrier licenses
45+
Countries, local numbers
140+
Round trip PoP to PoP
<200ms

Physics

Latency is decided by distance, not by the model

Teams try to solve latency by picking a faster model, when in reality, the dominant cost is distance and vendor boundaries. Co-location of infrastructure and services puts compute in the same rack as the media plane, removing the boundaries. This is something that the application layer can't fix.

EXPLORE DEV DOCS
GET api.telnyx.com/v2/ai/assistants/trace
# t+0     PSTN in Telnyx switch fra-pop-2# t+8ms   media plane RTP terminates, same rack# t+40ms  STT GPU, same rack# t+118ms LLM GPU, same rack# t+338ms TTS GPU, same rack# t+460ms audio out PSTN x-hops-to-pstn: 0x-public-internet-transits: 0x-vendors: 1

Sovereignty

Ownership enables sovereignty

Data residency follows from the network architecture, not from configuration. We hold the telecom license. We operate the regulated infrastructure inside the region. In-region processing is not a feature toggle. One data boundary, one DPA, one audit surface across compute, storage, and telephony.

Only audio crosses this boundary

In region

Telnyx, licensed in country

One building, same rack

  • Media plane (RTP)
  • Inference on owned GPUs
  • Transcripts and recordings
  • Embeddings and vector data
  • Object storage

One DPA, one vendor

Countries, SIP Trunking
140+
SIP calls per month
500M+
Messages per month
1.3B+
API requests per month
750M+

Composition

Every primitive on one control plane

The same blocks compose into a voice agent, a contact centre, a connected fleet, global notifications, or a private in-region deployment. One API, one bill, one support team, one compliance boundary.

Loading...

Ownership vs rented layers

Most platforms rent the network. We own it.

Every rented layer adds margin you pay, latency you feel, and a vendor boundary you debug. Here is what changes when one company owns the whole path.

CapabilityTelnyx - Global Communications Platform ProviderRented/aggregated
Carrier license, PSTN terminationOwned, 30+ countriesResold through aggregator
Fiber backbone between PoPsPrivately ownedPublic internet transit
GPU clusters colocated with media planeSame rack, same PoPSeparate cloud region, network hops
Edge compute at the PoPFunctions, KV, storage, actorsSeparate vendor, separate bill
STIR/SHAKEN attestationA-level, originating carrierB or C level, passthrough
In-region data sovereigntyBy architecture, not configConfigured per request, not guaranteed
Vendors in a single call path13 to 5
SLAs, bills, support teams11 per vendor

Agent-Native

The next buyer is an agent, and it can buy without us

The only claim in the framework no competitor contests. Agent-readable surfaces so coding agents can discover, price, and provision the stack without a human in the loop.

  • telnyx.com/llms.txt

    llms.txt

    A versioned, machine-readable description of every product, primitive, and capability. Live and kept in sync with the platform.

  • telnyx.com/ai/pricing.json

    /ai/pricing.json

    Pricing is a file, not a sales call. Versioned, programmatically consumable, and updated in real time.

  • api.telnyx.com/v2/mcp

    MCP Server

    Model Context Protocol server for direct agent interaction. Provision, configure, and manage resources without a UI.

  • telnyx.com/agent-signup.md

    agent-signup.md

    Signup is an API, not a sales queue. An agent can create an account, provision a number, and place a first call programmatically.

  • x402.telnyx.com

    x402 Endpoint

    Per-call payment in USDC. No account required. An agent can discover, price, and purchase a single call without a human.

  • developers.telnyx.com

    Agent-Readable Docs

    Documentation structured for parsing by coding agents. OpenAPI specs, quickstarts, and reference material that an agent can consume directly.

Build on the network, not over it.

Card on file, first primitive live in five minutes. Talk to an engineer who runs the network when you want peering, dedicated capacity, or a region.

FAQ

A point of presence is a site with Telnyx network, switching, GPU, and compute equipment that takes traffic off the public internet onto the private backbone and back out to the PSTN or a peer.