centaur-partners-api

Fetch and summarize Centaur partner trading data via MCP or REST.

1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/centaur-io/centaur-partners-skill --skill centaur-partners-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: centaur-partners-api
Source: https://github.com/centaur-io/centaur-partners-skill/tree/main
Command: npx skills add https://github.com/centaur-io/centaur-partners-skill --skill centaur-partners-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps agents and developers reliably retrieve, summarize, and generate requests for Centaur partner trading data while choosing the correct transport and protecting API keys. It removes guesswork about when to use MCP versus REST, enforces pagination and time-bounded reads, and provides clear guidance for presenting messages, events, positions, and stats.

Core Features & Use Cases

  • Transport selection: Prefer MCP when the client is configured, otherwise fall back to REST using CENTAUR_PARTNER_API_KEY or a one-time pasted partner key.
  • Data retrieval guidance: Instructions for events, messages, positions, and stats including pagination, start/end time bounds, and hiding system-generated events by default.
  • Curl and client setup: Generate correct GET /api/v1/* curl examples, and provide setup snippets for Claude, Cursor, and Codex MCP configuration.
  • Security controls: Treat pasted keys as transient, do not echo or persist keys, and avoid inventing credentials or unsupported auth flows.

Quick Start

Use the centaur-partners-api skill to fetch the last 10 events for a trader via MCP or REST and produce a concise summary highlighting trade outcomes and sentiment.

Frequently Asked Questions about centaur-partners-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve Centaur partner trading data using MCP or REST?

You can retrieve Centaur partner trading data by using MCP when the client is configured, or falling back to REST with an x-api-key or a one-time pasted partner API key for GET /api/v1/* endpoints.

What is the best way to generate pagination-aware curl requests for partner trading APIs?

The best way to generate pagination-aware curl requests is to use automated guidance that applies start and end time bounds, excludes system events by default, and formats correct GET /api/v1/* endpoint examples.

Does the Centaur partner API support fetching events, positions, and stats with time-bounded queries?

Yes, the Centaur partner API supports fetching events, messages, positions, and stats with pagination-aware listing, time-bounded queries, and default exclusion of system-generated events.

How do I configure MCP clients like Claude or Cursor for the Centaur partner API?

You can configure MCP clients by using provided setup snippets for Claude, Cursor, and Codex MCP configuration, ensuring the client is properly set up to handle transport selection automatically.

Can I persist a pasted partner API key for ongoing REST requests?

No, pasted partner API keys are treated as transient and must not be echoed, persisted, or invented, ensuring unsupported auth flows are avoided and credentials are protected.

When should I use MCP instead of REST for accessing partner trading data?

You should use MCP when the client is configured and available, otherwise falling back to REST with an x-api-key or one-time pasted partner key is necessary for data retrieval.