Regions & Endpoints

Amigo provides region-specific API endpoints to support data residency and latency requirements. If your organization is provisioned in a specific region, use the corresponding base URL. For organizations on dedicated clusters, you can also target your cluster explicitly via the x-mongo-cluster-name header.

Regional Base URLs

Region	Location	Base URL
US	N. Virginia (us-east-1)	https://api.amigo.ai
CA	Montreal (ca-central-1)	https://api-ca-central-1.amigo.ai
EU	Frankfurt (eu-central-1)	https://api-eu-central-1.amigo.ai
AU	Sydney (ap-southeast-2)	https://api-ap-southeast-2.amigo.ai

Coming Soon Additional regions (India, Middle East, Japan) are in development. Contact your Amigo representative to request access or discuss timelines.

Region Matching Required Use the regional base URL that matches your organization's data residency. Requests to a mismatched region will return "Organization not found" errors.

LLM Regional Availability

Not all LLMs are deployed in every region due to infrastructure constraints. When selecting version set presets, ensure the preset's LLMs are available in your target region.

LLM	US	CA	EU	AU
GPT-4.1, GPT-4.1-mini	✓	✓	✓	✓
GPT-5, GPT-5-mini, GPT-5-nano	✓	✓	✓	✓
GPT-5.1	✓	✗	✓	✗
Claude Sonnet 4.5 (Google/AWS)	✓	✓	✓	✓
Gemini 2.5 Pro/Flash	✓	✓	✓	✓

GPT-5.1 Regional Restriction

GPT-5.1 is only available in US and EU regions. The following presets use GPT-5.1 and cannot be deployed to CA or AU:

• text_premium

• async

• async_premium

Use forge channel validate-preset <preset> <channel> --region <region> to verify compatibility before deployment.

Global Deployment Map

cURL example

curl -X GET \
  -H "Authorization: Bearer <YOUR_JWT_TOKEN>" \
  "https://api-ca-central-1.amigo.ai/v1/<your-org-id>/organization/"

SDK configuration

Specify the regional base URL via the SDK base_url/baseUrl setting.

Python

from amigo_sdk import AmigoClient

with AmigoClient(
    api_key="<key>",
    api_key_id="<key-id>",
    user_id="<user>",
    organization_id="<org>",
    base_url="https://api-ca-central-1.amigo.ai",
) as client:
    org = client.organization.get()

TypeScript

Environment variables

You can also set the regional endpoint via environment variables.

# US
AMIGO_BASE_URL=https://api.amigo.ai

# CA
# AMIGO_BASE_URL=https://api-ca-central-1.amigo.ai

# EU
# AMIGO_BASE_URL=https://api-eu-central-1.amigo.ai

# AU
# AMIGO_BASE_URL=https://api-ap-southeast-2.amigo.ai

Dedicated Clusters

Some enterprises run on dedicated, isolated clusters. In these cases, include x-mongo-cluster-name to direct requests to your assigned cluster.

Cluster Name Your Amigo team will provide the exact cluster name if your tenant uses a dedicated cluster. Do not guess this value.

Header: x-mongo-cluster-name: <cluster-name>

When to use:

• Required: Organization provisioning (Create Organization)

• Recommended: Early provisioning flows when the organization may not yet be discoverable via the global config

• Optional: Normal operations for established organizations — most endpoints do not require it once your org is fully set up

cURL Example (Dedicated Cluster)

curl -X PUT \
  -H "Authorization: Bearer <YOUR_JWT_TOKEN>" \
  -H "x-mongo-cluster-name: <your-dedicated-cluster-name>" \
  -H "Content-Type: application/json" \
  "https://api-eu-central-1.amigo.ai/v1/<your-org-id>/organization/" \
  -d '{
    "org_name": "Example Corp",
    "title": "Example Corp AI",
    "main_description": "Intelligent assistants for Example Corp",
    "sub_description": "Personalized, compliant AI",
    "user_dimensions": [],
    "logo": "<base64>",
    "square_logo": "<base64>",
    "favicon": "<base64>",
    "signup_page_headshot": "<base64>",
    "default_user_preferences": {},
    "onboarding_instructions": ["Welcome to Example Corp AI"],
    "azure_devops_team_name": "example-team"
  }'

SDK examples (dedicated cluster)

Python

# If your SDK version exposes a raw HTTP method, include the header
# for organization provisioning requests. Otherwise, use cURL as shown above.

TypeScript

Recommendations

Best Practices

1. Confirm your organization's region with your Amigo representative and set the matching base URL

2. For dedicated cluster tenants, store your cluster name in a secure configuration store

3. Include the x-mongo-cluster-name header where instructed for dedicated clusters

Troubleshooting "Organization not found"

If you encounter this error:

• Verify you are calling the correct regional base URL

• For provisioning flows, ensure the x-mongo-cluster-name header is set (if on dedicated cluster)