Telnyx

Inference locations

Provider API declarations are also available on each model's endpoint API. Direct chat and Responses replies separate advertised availability from serving location in usage.inference_location; the actual serving region remains unknown when not reported.

usage.provider_usage.gateway_region identifies the TrustedRouter gateway, not the provider's inference location. A value such as europe-west4 does not mean the model ran in Europe. usage.inference_location.serving_region remains null when the provider has not reported it. Older gateways may return the gateway-only field as provider_usage.region.

Where the upstream GPUs execute the model, not the provider's headquarters, API ingress, or data storage. ZDR and confidential inference do not by themselves restrict geography.

Declared countries or regions

United States; Europe (Telnyx EU region; countries unspecified); Australia; United Arab Emirates
Provider-wide GPU region set. Model availability is narrower; see the catalog snapshot below. Germany in the storage-locality documentation does not establish Germany as the inference country.

Can locations change?

Dynamic, latency-based routing by default. Regional ingress is a preference; capacity events and failover can move inference to another available region. Model deployments may change.

Provider region pinning

Telnyx documents region + mode: strict on a matching regional ingress domain for its own hosted models. Requests fail if the selected region cannot serve them. Preferred mode is not a residency guarantee.

Pinning through TrustedRouter

Not supported by the current TrustedRouter integration: it uses api.telnyx.com without Telnyx's strict region controls. Do not send Telnyx-specific region/mode fields as a TrustedRouter pin.

Infrastructure declaration

Multi-region, dynamically routed among the model's available Telnyx regions; no fixed inference-region commitment on this TrustedRouter route.

Evidence

Public documentation and authenticated model catalog. Reviewed 2026-09-26.

• Inference regions and strict pinning
• Processing versus storage
• Native model catalog (authentication required)

Provider selection alone is not a region pin. TrustedRouter's US provider filter selects company jurisdiction, not GPU location. A regional gateway hostname does not pin a downstream GPU. For a binding residency requirement, confirm the model, region, failover scope and enforced controls before sending sensitive data.