Regions & Endpoints

Configure regional Platform, identity, service, and Console hosts, distinguish Classic endpoints, and migrate clients without relying on legacy redirects.

Concurrence's APIs are deployed across multiple regions to reduce latency and support data residency requirements. Each region operates independently with its own compute and AI routing. This page lists the regional base URLs for both the Classic API and the Platform API, explains how routing differs between the two, and covers dedicated cluster headers.

Regional Base URLs

Concurrence runs in four regions. Use the tables below to find the base URL for each API.

Classic API

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

Platform API

Slot	Location	Base URL
us	N. Virginia (us-east-1), production	https://platform.api-us.concurrence.com
ca	Montreal (ca-central-1), production	https://platform.api-ca.concurrence.com
eu	Frankfurt (eu-central-1), production	https://platform.api-eu.concurrence.com
au	Sydney (ap-southeast-2), production	https://platform.api-au.concurrence.com
staging	Staging, when provisioned	https://platform.api-staging.concurrence.com

Identity and Developer Console

Use the same assigned slot for Platform resources, identity, and Console. The identity base is separate from the Platform API base.

Slot	Identity base URL	Developer Console
us	https://identity.api-us.concurrence.com	https://console-us.concurrence.com
ca	https://identity.api-ca.concurrence.com	https://console-ca.concurrence.com
eu	https://identity.api-eu.concurrence.com	https://console-eu.concurrence.com
au	https://identity.api-au.concurrence.com	https://console-au.concurrence.com
staging	https://identity.api-staging.concurrence.com	https://console-staging.concurrence.com

Service-Specific Hosts

Replace <slot> with the assigned staging, us, au, eu, or ca slot. These are hostname patterns, not a promise that every service is provisioned in every slot. Keep the documented route path; select its owning service rather than sending every request to the Platform API host.

Service	Canonical HTTPS host	Routing boundary
Platform API	platform.api-<slot>.concurrence.com	/v1/*, /s/*, and Platform MCP protected-resource metadata
Agent engine	agent-engine.api-<slot>.concurrence.com	Returned call/observer connection URLs under /voice-agent/ or /agent/; use wss:// for WebSockets. Also serves live call context at /agent/calls/{call_sid}/context
Identity	identity.api-<slot>.concurrence.com	/token, /device/*, identity /.well-known/*, and login /sessions routes
Data-MCP	data-mcp.api-<slot>.concurrence.com	/data-mcp/*; not the Platform /v1/mcp endpoint
Bridge	bridge.api-<slot>.concurrence.com	/livekit-webhook
SMS	sms.api-<slot>.concurrence.com	/outbound-sms; workspace SMS operations remain on Platform
Connector runner	connector-runner.api-<slot>.concurrence.com	Retired October 10, 2026; see Connector Runner
Developer Console	console-<slot>.concurrence.com	Console pages and Console-owned API routes
Forms	forms.api-<slot>.concurrence.com	Provisioned form URLs
Scribe	scribe.api-<slot>.concurrence.com	Scribe sessions, artifacts, and its separate schema
Tool manager	tool-manager.api-<slot>.concurrence.com	Provisioned tool-management endpoints
Zoom meeting bot	zoom-meeting-bot.api-<slot>.concurrence.com	Provisioned meeting-bot endpoints
Channel Manager	channels.api-us.concurrence.com	Documented US production channel API, /openapi.json, and /redoc

Migrating Existing Clients

1. Set Platform and identity base URLs separately. The Platform SDK's baseUrl takes an origin without /v1; device-code helpers take identityBaseUrl. Forge profiles have separate --api-url and --identity-url options.

2. Configure token helpers against the identity host. From Platform SDK 0.113.1, client.tokens.* uses identityBaseUrl, then baseUrl; set identityBaseUrl whenever you set baseUrl, as shown in SDK Configuration.

3. Use returned connection URLs for calls and observers. The workspace text socket /v1/{workspace_id}/sessions/connect stays on the Platform host; login /sessions routes belong to identity. Check Text Sessions before changing WebSocket configuration.

4. Update relevant allowlists, provider callback URLs, and saved Console bookmarks. Preserve credentials, scopes, workspace IDs, package names, and imports.

The legacy *.platform.amigo.ai hosts no longer resolve. They stopped resolving on October 14, 2026, so a client, allowlist, or bookmark that still names one fails before reaching the platform, and nothing redirects it. Configure the canonical hosts above directly and test your client's authentication and connection behavior. Identity discovery also requires the rollout check before enabling discovery-based clients.

How routing differs between the APIs

• Classic API: region matching is required. Use the base URL that matches your organization's data residency. Requests to a mismatched region return "Organization not found" errors.

• Platform API: region matching is required. https://platform.api-us.concurrence.com is the US endpoint, not a global router. Use the deployment hostname agreed during provisioning and store it with the integration configuration. A workspace response reports the serving deployment's region; it is not a mutable placement policy. The accepted legacy region-update field is ignored and does not migrate data.

AI-backed service and model availability can differ by deployment. Do not infer that every external model or processor runs in the workspace region; confirm the data path and regional availability for the features you enable.

Contact your Concurrence representative for regional availability and upcoming regions.

For organizations on dedicated clusters, you can also target your cluster explicitly via the x-mongo-cluster-name header - see Dedicated Clusters below.

Confirm Each Service

Regional Platform and Classic API hosts identify those API deployments. Confirm Scribe, managed channels, provider integrations, and any external processors separately before adding them to a workflow. Use the service-specific mapping only for a confirmed deployment; substituting a slot into a hostname does not establish service availability.

Capability	Regional readiness to verify
Platform workspace resources	Assigned Platform host, workspace access, and required features enabled in that deployment
Classic integration	Assigned Classic host and organization; use the Classic credential flow
Scribe and Zoom capture	Assigned Scribe base, provider enrollment, supported capture setup, and permitted processing location
Managed phone and messaging	Provisioned line/account and binding, regional support, and delivery/processing constraints
External data and model processing	Approved source/destination and the applicable data-processing boundary

Record the confirmation owner, test evidence, limitations, and date using Govern a Deployment. The public US Scribe schema establishes an HTTP contract, not availability in every Platform region. Data Residency explains the broader deployment review.

LLM Regional Availability

Not all LLMs are deployed in every region. When selecting version set presets, make sure the preset's LLMs are available in your target region.

Confirm model and feature availability for the intended deployment. A preset name does not guarantee that every model or external processor is available in every region.

The legacy Python Agent Forge build provides forge channel llm-info and forge channel validate-preset <preset> <channel> --region <region> for Classic channel presets. These commands are not part of the current Go CLI's Platform-only command surface.

Classic preset compatibility. Legacy preset and Python Forge instructions belong to Classic channel tagging. Confirm the current model and processor availability for the actual deployment before reusing a historical preset. These presets do not establish Platform regional support.

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 or baseUrl setting.

Classic 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()

Classic TypeScript

import { AmigoClient } from "@amigo-ai/sdk";

const client = new AmigoClient({
  apiKey: process.env.AMIGO_API_KEY!,
  apiKeyId: process.env.AMIGO_API_KEY_ID!,
  userId: process.env.AMIGO_USER_ID!,
  orgId: process.env.AMIGO_ORGANIZATION_ID!,
  baseUrl: "https://api-ca-central-1.amigo.ai",
});

const org = await client.organizations.getOrganization();

Platform TypeScript

import { AmigoClient } from '@amigo-ai/platform-sdk'

const client = new AmigoClient({
  apiKey: process.env.AMIGO_PLATFORM_API_KEY!,
  workspaceId: process.env.AMIGO_WORKSPACE_ID!,
  baseUrl: 'https://platform.api-ca.concurrence.com',
})

const workspace = await client.workspaces.get()

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

This section covers Classic organization provisioning. It does not configure Platform workspace placement.

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 Concurrence team provides 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",
    "user_dimensions": [],
    "logo": "<base64>",
    "square_logo": "<base64>",
    "favicon": "<base64>",
    "default_user_preferences": {},
    "azure_devops_team_name": "example-team"
  }'

The SDKs do not currently expose a raw-header helper; use cURL for dedicated-cluster provisioning requests.

Recommendations

Best practices

1. Confirm your organization or workspace region with your Concurrence 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 see this error:

• Verify you are calling the correct regional base URL.

• For provisioning flows, make sure the x-mongo-cluster-name header is set (if you are on a dedicated cluster).