Rebrand and Compatibility

Amigo is now Concurrence. Understand the documentation rebrand and which service domains changed and which API hosts, SDK packages, and identifiers remain.

Amigo is now Concurrence. The documentation uses the Concurrence name and approved logo artwork. The canonical documentation site is docs.concurrence.com.

What Changed

The September 19, 2026 documentation release updates current product descriptions, navigation labels, diagrams, and generated LLM exports. Cross-space links use the new documentation domain. GitHub repository links use the concurrence-hq organization.

Published page paths and existing heading anchors remain stable. Some paths still contain amigo, including overview and historical API changelog paths. Use the new documentation domain with those same paths; a brand change alone is not a reason to rename an integration.

Platform Service Domains

Platform services and Developer Console now have service-specific concurrence.com addresses. For US production, use https://platform.api-us.concurrence.com for Platform resources, https://identity.api-us.concurrence.com for identity token/device/login-session routes, and https://console-us.concurrence.com for Console. The deployment slots are staging, us, au, eu, and ca; us is production in us-east-1.

Use Regions and Endpoints for the complete service mapping and regional configuration. Update API clients, auth configuration, provider callbacks, and allowlists explicitly. Do not replace every former shared API URL with the Platform hostname: identity, agent connections, and Data-MCP have their own hosts.

The September 20, 2026 checks found legacy API, Console login, and Channel Manager URLs still serving responses rather than universally redirecting to the new domains. Configure canonical hosts directly instead of depending on redirects, including for authentication and WebSocket clients. The CLI installer host is not part of this service-domain mapping.

What Stays the Same

The service-domain migration does not change the documented credential types and resource identifiers. Continue using the credentials and scopes provisioned for your deployment. SDK packages keep their names, with one exception: the Scribe TypeScript SDK now publishes under the @concurrence-hq npm scope.

Integration surface	Current name or behavior
Classic API hosts	The documented amigo.ai hosts, including api.amigo.ai and its regional equivalents; the Platform service migration does not include Classic
Platform TypeScript SDK	@amigo-ai/platform-sdk, including AmigoClient
Classic TypeScript SDK	@amigo-ai/sdk
Classic Python SDK	amigo-sdk, imported as amigo_sdk
Scribe TypeScript SDK	@concurrence-hq/scribe-typescript-sdk (renamed). @amigo-ai/scribe-typescript-sdk is deprecated and receives no updates
Environment variables and headers	Existing identifiers such as AMIGO_API_KEY and X-AMIGO-CHANNEL-MANAGER-WEBHOOK-SIGNATURE
Authentication and resources	Existing credentials, scopes, and organization/workspace identifiers
API schema imports	Existing OpenAPI registry identifiers, including amigo-api

Do not replace amigo with concurrence in package names, imports, or wire identifiers as a branding substitution. Change a package name only when the table above lists a new name: today that is only the Scribe TypeScript SDK, so update its install command and import path to @concurrence-hq/scribe-typescript-sdk. The Platform SDK, Classic SDKs, and all wire identifiers keep their amigo names. The legacy *.platform.amigo.ai hosts stopped resolving on October 14, 2026. Platform SDK 0.113.1 and later default to the concurrence.com hosts; older packages and saved CLI profiles that name a legacy host must be updated, so set endpoint options explicitly. For deployment-specific hosts and credentials, follow Regions and Endpoints and Authentication.

Reading Older Material

Older release entries and product screenshots can still say Amigo. They describe the name and interface in use at the time, not a separate current product. Use the current guides and public API schemas for present behavior; use Change Logs and Upgrade Guidance when reviewing integration changes.