Migrating from partners.centaur.io - Centaur Docs

The Centaur API now has its own hosts. Endpoints, responses, scopes and REST API keys are unchanged. MCP clients reconnect to the new URL and may need to sign in again.

Surface	Old URL	New URL
REST v2	`https://partners.centaur.io/api/v2`	`https://api.centaur.io/v2`
REST v1	`https://partners.centaur.io/api/v1`	`https://api.centaur.io/v1`
OpenAPI	`https://partners.centaur.io/api/v2/openapi.json`	`https://api.centaur.io/v2/openapi.json`
MCP	`https://partners.centaur.io/mcp`	`https://mcp.centaur.io/mcp`

Timeline

For one month after the new hosts launch, partners.centaur.io keeps serving REST and MCP as before. During that month api.centaur.io also accepts the old /api/v1 and /api/v2 paths.
After that month, REST paths on partners.centaur.io return 308 redirects to api.centaur.io with the /api segment removed.
https://partners.centaur.io/mcp then returns 410 with a pointer to the new URL, because MCP clients do not follow redirects.

What to change

REST: replace the base URL and keep sending x-api-key. Update the URL directly rather than relying on the redirect.
MCP: remove the old server in your client and add https://mcp.centaur.io/mcp. Your client may ask you to sign in and approve access again.

Last modified on September 29, 2026