Skip to main content
Use this page to choose the right Centaur read surface without scanning the full generated reference first.

Capability map

Data familyREST endpointMCP toolRequired scopeNotes
Trader discoveryGET /api/v1/traderslist_tradersdirectory.readDiscover traders directly by name or related asset filters before calling detail stats.
Asset discoveryGET /api/v1/assetslist_assetsdirectory.readDiscover assets directly by name or symbol before calling detail stats.
EventsGET /api/v1/eventslist_eventsevents.readHistorical trade-event feed with position, asset, trader, and source context.
MessagesGET /api/v1/messageslist_messagesmessages.readMessage feed deduplicated on channel and message identity, with compatibility event narrowing when requested.
Valid closed positionsGET /api/v1/positions/closed/validlist_valid_closed_positionspositions.readClosed positions with realized returns, excluding invalid closes.
Open positionsGET /api/v1/positions/openlist_open_positionspositions.readCurrently open positions with current marks and unrealized returns.
Trader statsGET /api/v1/traders/{traderId}/statsget_trader_statsstats.readAggregate performance and positioning metrics for one trader.
Asset statsGET /api/v1/assets/{assetId}/statsget_asset_statsstats.readAggregate positioning and top-trader metrics for one asset.

Observable behavior across reads

  • Operations are scope-gated. A key may work on some endpoint families and return 403 on others.
  • Historical list reads and stats responses echo the applied bounds back to you after server-side clamping.
  • Some rows may be omitted because they are deleted, tied to ineligible connected entities, or outside the current access policy. Omitted rows do not produce placeholder warnings.
  • Cursor pagination always reflects the current eligible result set, not a frozen snapshot.

Example: asset discovery

curl -s 'https://partners.centaur.io/api/v1/assets?search=bitcoin&limit=10' \
  -H 'x-api-key: <partner-api-key>'

Example: messages

curl -s 'https://partners.centaur.io/api/v1/messages?eventTypes=open,close&startTime=2026-03-01T00:00:00.000Z&limit=10' \
  -H 'x-api-key: <partner-api-key>'
By default, GET /api/v1/messages returns eligible messages even when no extracted events are linked to them. If you pass assetIds, directions, or eventTypes, those act as compatibility filters and only keep messages with at least one linked event that matches.

Example: valid closed positions

curl -s 'https://partners.centaur.io/api/v1/positions/closed/valid?assetIds=34&limit=10' \
  -H 'x-api-key: <partner-api-key>'

Example: trader stats

curl -s 'https://partners.centaur.io/api/v1/traders/17/stats?startTime=2026-03-01T00:00:00.000Z&endTime=2026-03-31T23:59:59.999Z' \
  -H 'x-api-key: <partner-api-key>'

Next steps

Last modified on April 17, 2026