> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.talqora.com/get-started/regional-api-endpoints/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.talqora.com/_mcp/server.

# Regional API endpoints

Talqora exposes the same Vector API through a default endpoint and regional endpoint aliases. Every endpoint accepts the same `tq_live_` API keys and exposes the same `/v1` routes.

## Default endpoint for every plan

All plans should use `https://api.talqora.com`. It is the stable public API origin for Developer, Scale, and Enterprise workspaces; it routes each request to the immutable region of its target index. You do not need to select a hostname based on where an index was created.

Regional aliases are an Enterprise-only capability. They are enabled by Talqora as part of an Enterprise regional deployment or a [BYOC deployment](/operate-at-scale/byoc). They are not required for data residency: the index region, rather than the hostname, determines where dense and sparse retrieval runs.

| Endpoint                               | Intended routing region |
| -------------------------------------- | ----------------------- |
| `https://api.talqora.com`              | Default endpoint        |
| `https://us-east.api.talqora.com`      | Americas, US East       |
| `https://sa-east.api.talqora.com`      | Latin America           |
| `https://eu-west.api.talqora.com`      | Europe                  |
| `https://ap-southeast.api.talqora.com` | Asia Pacific            |

Enterprise teams can use a regional endpoint in server-side applications when it is closer to their workload. For browser applications, continue to use `https://api.talqora.com` unless your CORS policy explicitly permits a regional hostname.

## Index placement is explicit

The endpoint hostname is a routing preference. It does **not** move an index, change authorization, or create a separate workspace.

An index's `aws_region`, selected at creation time, determines where its dense vector store and sparse retrieval data are placed. Keep writes and queries near the index's configured AWS region for the lowest end-to-end latency.

```bash
curl https://sa-east.api.talqora.com/v1/indexes/$INDEX_ID/query \
  -X POST \
  -H "Authorization: Bearer $TALQORA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"top_k": 10, "vector": [0.01, 0.02]}'
```

Regional aliases are optional. Existing integrations using `https://api.talqora.com` continue to work unchanged. Contact Talqora to enable an Enterprise regional alias or to plan a BYOC deployment.