Skip to main content
Centaur Partners API gives external partners read-only access to Centaur partner data over two surfaces:
  • REST for direct HTTP integrations and predictable HTTP control.
  • MCP for agent-native clients such as Claude, Cursor, Codex, and ChatGPT.

​
How to get access

Once provisioned:
  • REST continues to use x-api-key: <partner-api-key>
  • MCP prefers the plain server URL https://partners.centaur.io/mcp and lets compatible clients dynamically register themselves before the browser-based OAuth approval flow
  • MCP keeps legacy API-key auth as a compatibility fallback for clients that cannot complete the OAuth flow yet

​
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

curl -s 'https://partners.centaur.io/api/v1/events?limit=10' \
  -H 'x-api-key: <partner-api-key>'
REST is the better fit when:
  • 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: 
https://partners.centaur.io/mcp
If your current client build cannot complete the OAuth handshake or registration flow yet, use the compatibility setup instructions in the client-specific guides. Those guides cover:
  • Authorization: Bearer <partner-api-key> where custom headers are supported
  • https://partners.centaur.io/mcp?api_key=<partner-api-key> only for clients that cannot send headers at all
For a manual smoke test, this compatibility request still works: 
curl -s 'https://partners.centaur.io/mcp' \
  -H 'accept: application/json, text/event-stream' \
  -H 'content-type: application/json' \
  -H 'authorization: Bearer <partner-api-key>' \
  -d '{"jsonrpc":"2.0","id":"tool-call-1","method":"tools/call","params":{"name":"list_events","arguments":{"limit":10}}}'
MCP is the better fit when:
  • 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
For most MCP onboarding, start with Client setup. Install the Public skill as an optional next step after the client is working.

​
What you can read

Data familyRESTMCPRequired scope
Trader discoveryGET /api/v1/traderslist_tradersdirectory.read
Asset discoveryGET /api/v1/assetslist_assetsdirectory.read
EventsGET /api/v1/eventslist_eventsevents.read
MessagesGET /api/v1/messageslist_messagesmessages.read
Valid closed positionsGET /api/v1/positions/closed/validlist_valid_closed_positionspositions.read
Open positionsGET /api/v1/positions/openlist_open_positionspositions.read
Trader statsGET /api/v1/traders/{traderId}/statsget_trader_statsstats.read
Asset statsGET /api/v1/assets/{assetId}/statsget_asset_statsstats.read
Use Available data reads for example requests and a compact cross-surface capability map. GET /api/v1/messages and list_messages behave as a message feed by default. If you pass assetIds, directions, or eventTypes, those filters narrow through linked events and exclude eventless messages for that request.

​
Service surfaces

​
What this product exposes today

  • REST reads under /api/v1/*
  • MCP reads at /mcp
  • shared read families across events, messages, positions, discovery, and stats
  • server-discovered MCP tools and resources for the current live contract
Install the public Centaur skill with or browse it at .
Last modified on April 20, 2026