# CoinPaprika integration instructions

Content reviewed: 2026-10-09.

1. Read [capabilities](https://coinpaprika.com/api/capabilities.json) for hosts, current plan definitions and licences. Interpret `monthly_calls_unlimited: true` as no monthly cap, not a missing quota. A rate limit still applies.
2. Connect to https://mcp.coinpaprika.com/streamable-http, discover `tools/list`, and inspect each tool’s `inputSchema`. The exported schemas are a dated live discovery snapshot.
3. Resolve ambiguous names into canonical asset IDs. Confirm chain and full contract addresses for tokens.
4. Include the required `rationale` argument (20–500 characters) where declared. Explain purpose without secrets or personal data.
5. Quote source `last_updated`, currency and the applicable refresh interval. Never present static website examples as current prices or confuse fetch time with source time.
6. Free is personal use; paid self-serve is internal commercial use. Customer-facing distribution requires an Enterprise contract.
7. Hosted MCP serves free-tier data. Run the local server with your paid key for paid tools. Keep paid keys server-side, in environment variables; the Authorization value is the key itself, without Bearer.
8. Inspect error bodies. Back off on 429 with bounded retries and jitter; check plan/quota restrictions on 402 and IDs on 404. Do not silently replace a failed request with a stale price.
9. CoinPaprika market data does not execute trades or move funds. `submitFeedback` is a write action; do not call it as part of read-only analysis without user intent.
10. Use the full OpenAPI schemas for typed integrations, and verify endpoint behaviour in your deployment before launch.

Authoritative sources: https://docs.coinpaprika.com/, https://coinpaprika.com/api/pricing, https://coinpaprika.com/api-terms-of-use/.