Default Endpoint
The default endpoint (llm-gateway.assemblyai.com) processes your LLM Gateway requests in the US region. If you don’t specify a base URL, this is the endpoint used by default.
EU Data Residency
The EU endpoint (llm-gateway.eu.assemblyai.com) guarantees your data never leaves the European Union. This is designed for organizations with strict data residency and governance requirements—your request and response data will remain entirely within the EU.
Endpoints
| Endpoint | Base URL | Description |
|---|---|---|
| US (default) | https://llm-gateway.assemblyai.com/v1/chat/completions | Data stays in the US |
| EU | https://llm-gateway.eu.assemblyai.com/v1/chat/completions | Data stays in the EU |
EU model availability
The EU endpoint currently supports Anthropic Claude and Google Gemini models. OpenAI models are only available through the US endpoint.| Provider | US | EU |
|---|---|---|
| Anthropic Claude | Yes | Yes |
| Google Gemini | Yes | Yes |
| OpenAI GPT | Yes | No |
| Alibaba Cloud Qwen | Yes | No |
| Moonshot AI Kimi | Yes | No |
Which endpoint should I use?
- No data residency requirements? Use the default endpoint. No configuration change is needed.
- Need EU data residency? Use the EU endpoint to ensure your data stays within the European Union. Note that only Claude and Gemini models are available in the EU region.
- No data residency, compliance, or latency needs, and want cheaper calls? Opt into global routing on top of the default endpoint to route requests to the provider’s global endpoints at lower cost.
How to use it
Update your request URL to your preferred endpoint. Select an endpoint tab below to see examples for each.- US (default)
- EU data residency
The US endpoint is the default. No configuration change is required.
Global routing
Global routing is an opt-in option that routes your request to the provider’s global (non-region) endpoints for lower-cost processing. Setmodel_region to "global" in your request body to enable it. Omit the parameter for default in-region processing.
"global" is the only valid value for model_region.
Who should use global routing?
Global routing is designed for customers who:- Do not have data residency or compliance requirements that tie processing to a specific region.
- Do not have strict latency requirements that depend on regional proximity.
- Want lower-cost calls by using the provider’s global endpoints.
model_region, requests continue to be processed in-region (US or EU), so data residency and compliance remain the default behavior. If you have data residency, compliance, or latency needs, keep using the default in-region processing on the US or EU endpoint.
Availability
Global routing is live for Anthropic Claude models. Support for Google Gemini 3 series models is coming soon.Usage tracking
Global-routed usage appears as a new Global region in the spend and usage dashboard, separate from US and EU usage.How to use it
Includemodel_region: "global" in your request body alongside model and messages.