RESTfor direct HTTP integrations and predictable HTTP control.MCPfor agent-native clients such as Claude, Cursor, Codex, and ChatGPT.
How to get access
Once provisioned:RESTusesx-api-key: <api-key>MCPprefers the plain server URLhttps://partners.centaur.io/mcpand lets compatible clients dynamically register themselves before the browser-based OAuth approval flow
Choose your integration path
REST quickstart
Choose REST when you want a conventional backend integration, predictable request/response behavior, and explicit
control over retries and pagination.
MCP quickstart
Choose MCP when your users work in Claude, Cursor, Codex, or another MCP-capable client and you want native tool
calling instead of handwritten HTTP requests.
REST quickstart
- you are integrating from a service or backend job
- you want explicit request and retry control
- you want the generated API reference to be your primary technical source
MCP quickstart
Preferred MCP onboarding uses the plain server URL. In supported clients, Centaur exposes Dynamic Client Registration for public clients before opening the browser sign-in and consent flow:- your users work in Claude, ChatGPT, Cursor, or Codex
- you want Centaur exposed as a tool instead of a raw HTTP dependency
- you want to pair the MCP surface with the public Centaur skill repo
What you can read
Use Available data reads for examples and the compact cross-surface capability map. Use Contract limits for unsupported single-read requests and agent caveats.
Service surfaces
What this product exposes today
- REST reads under
/api/v1/* - MCP reads at
/mcp - shared read families across the partner feed, events, messages, Generated Channel Narrative Summaries, Generated Aggregate Narrative Summaries, positions, discovery, stats, rankings, and activity summaries
- server-discovered MCP tools and resources for the current live contract