> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/reference/concurrence-rebrand.md).

# Rebrand and Compatibility

The Concurrence name and service domains, and which API hosts, SDK packages, and identifiers keep the Amigo name.

**Concurrence is the product and company name.** The documentation uses the Concurrence name and approved logo artwork. The canonical documentation site is [docs.concurrence.com](https://docs.concurrence.com).

## Documentation <a href="#what-changed" id="what-changed"></a>

Product descriptions, navigation labels, diagrams, and generated LLM exports use the Concurrence name. Cross-space links use the docs.concurrence.com domain. GitHub repository links use the `concurrence-hq` organization.

Published page paths and existing heading anchors remain stable. Some paths contain `amigo`, including overview and historical API changelog paths. Use the docs.concurrence.com 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 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 the US production slot.

Use [Regions and Endpoints](https://docs.concurrence.com/developer-guide/getting-started/regions-and-endpoints) for the complete service mapping and regional configuration. Update API clients, auth configuration, provider callbacks, and allowlists explicitly. Do not point every client at the Platform hostname: identity, agent connections, and Data-MCP have their own hosts.

Configure canonical hosts directly instead of depending on redirects, including for authentication and WebSocket clients.

## Retained Identifiers <a href="#what-stays-the-same" id="what-stays-the-same"></a>

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 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 `*.platform.amigo.ai` hosts do not resolve. Platform SDK 0.113.1 and later default to the `concurrence.com` hosts; update older packages and saved CLI profiles that name a `*.platform.amigo.ai` host, or set endpoint options explicitly. For deployment-specific hosts and credentials, follow [Regions and Endpoints](https://docs.concurrence.com/developer-guide/getting-started/regions-and-endpoints) and [Authentication](https://docs.concurrence.com/developer-guide/getting-started/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](https://docs.concurrence.com/api-reference/change-logs) and [Upgrade Guidance](https://docs.concurrence.com/api-reference/change-logs/upgrade-guide) when reviewing integration changes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/reference/concurrence-rebrand.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.