coinpaprika-api
Über
Diese Claude Skill ermöglicht HTTP-Anfragen an die CoinPaprika API für Kryptowährungsmarktdaten wie Preise, Ticker und historische OHLCV-Daten. Sie bietet Zugriff auf Daten zu Tausenden von Coins und Börsen, wobei eine kostenlose Nutzungsstufe ohne API-Schlüssel verfügbar ist. Verwenden Sie diese Funktion, wenn Ihre Anwendung Echtzeit- oder historische Kryptomarktstatistiken von api.coinpaprika.com abrufen muss.
Schnellinstallation
Claude Code
Empfohlennpx skills add coinpaprika/skills -a claude-code/plugin add https://github.com/coinpaprika/skillsgit clone https://github.com/coinpaprika/skills.git ~/.claude/skills/coinpaprika-apiKopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um diese Fähigkeit zu installieren
Dokumentation
CoinPaprika API Skill
Independent cryptocurrency data aggregator since 2018. 12,000+ cryptocurrencies, 350+ exchanges, $2.4T+ market cap coverage. Free tier available with no API key required.
- Documentation: https://docs.coinpaprika.com
- LLM-readable docs: https://docs.coinpaprika.com/llms-full.txt
- Pricing: https://coinpaprika.com/api/pricing
- GitHub: https://github.com/coinpaprika
- Support: [email protected]
Base URLs and authentication
Free tier (no key required)
https://api.coinpaprika.com/v1/
20,000 calls/month, 2,000 assets. No API key, no registration.
curl -s "https://api.coinpaprika.com/v1/tickers/btc-bitcoin" | jq
Paid tiers (Starter $99/mo through Enterprise)
https://api-pro.coinpaprika.com/v1/
Requires API key in the Authorization header:
curl -s "https://api-pro.coinpaprika.com/v1/tickers/btc-bitcoin" \
-H "Authorization: ${COINPAPRIKA_API_KEY}" | jq
Never hardcode API keys. Store in environment variables:
export COINPAPRIKA_API_KEY="your_key_here"
Plan comparison
| Plan | Price | Calls/month | Assets |
|---|---|---|---|
| Free | $0 | 20,000 | 2,000 |
| Starter | $99 | 400,000 | All |
| Pro | $199 | 1,000,000 | All |
| Business | $799 | 5,000,000 | All |
| Enterprise | Custom | Unlimited | All |
Rate limit: 10 requests/second per IP across all plans.
Integration options
Option 1: REST API (primary)
All endpoints below. Use the appropriate base URL for the tier.
Option 2: CLI
https://github.com/coinpaprika/coinpaprika-cli
Crypto market data from the terminal. 8,000+ coins, real-time prices, OHLCV, exchanges. Free tier included.
For CLI command reference, read references/cli-reference.md.
Option 3: MCP Server (for AI IDEs)
Hosted MCP server for Claude Desktop, Cursor, Windsurf, and any MCP client.
Add to claude_desktop_config.json or equivalent:
{
"mcpServers": {
"coinpaprika": {
"url": "https://mcp.coinpaprika.com/sse"
}
}
}
No API key needed for the hosted version. Provides 30+ tools for querying coins, tickers, exchanges, OHLCV, contracts, tags, and search.
Option 4: SDKs
LLM-readable documentation
Full API spec in Markdown for direct LLM consumption:
All endpoints
Global
GET /global # Market overview data
Coins
GET /coins # List all coins
GET /coins/{coin_id} # Coin details (e.g., btc-bitcoin)
GET /coins/{coin_id}/events # Coin events
GET /coins/{coin_id}/exchanges # Exchanges listing a coin
GET /coins/{coin_id}/markets # Trading pairs for a coin
GET /coins/{coin_id}/ohlcv/historical # Historical OHLCV (?start, ?end, ?interval, ?limit, ?quote)
GET /coins/{coin_id}/ohlcv/latest # Last full day OHLCV
GET /coins/{coin_id}/ohlcv/today # Today's OHLCV (partial)
GET /coins/{coin_id}/twitter # DEPRECATED
Tickers (price data)
GET /tickers # All tickers (?quotes=USD,BTC)
GET /tickers/{coin_id} # Specific coin ticker
GET /tickers/{coin_id}/historical # Historical ticks (?start, ?end, ?interval, ?limit, ?quote)
Exchanges
GET /exchanges # List all exchanges
GET /exchanges/{exchange_id} # Exchange details
GET /exchanges/{exchange_id}/markets # Exchange markets
Contracts
GET /contracts # List contract platforms
GET /contracts/{platform_id} # Contracts on a platform
GET /contracts/{platform_id}/{contract_address} # Ticker by contract (301 redirect)
GET /contracts/{platform_id}/{contract_address}/historical # Historical by contract (301 redirect)
Note on contract ticker/historical: These return 301 redirects to /tickers/{coin_id}. The Location header may use http:// instead of https://. Handle the redirect manually by reading the Location header, fixing the scheme to https://, and making a second request with the Authorization header.
Verified response shapes:
GET /contractsreturns a flat string array:["btc-bitcoin", "eos-eos", "eth-ethereum", ...]GET /contracts/{platform_id}returns:[{"address": "0xa974...", "type": "ERC20", "id": "xin-mixin", "active": true}]
Tags
GET /tags # List all tags
GET /tags/{tag_id} # Tag details
GET /tags/{tag_id}?additional_fields=coins # Tag with coin IDs
GET /tags/{tag_id}?additional_fields=coins,icos # Tag with coins and ICOs
People
GET /people/{person_id} # Person details (e.g., vitalik-buterin)
Search and tools
GET /search?q={query}&c={categories}&limit={n} # Search (categories: currencies,exchanges,icos,people,tags)
GET /price-converter?base_currency_id={from}"e_currency_id={to}&amount={n}
Key info (paid tiers only)
GET /key/info # API key details and usage
Response: {"plan", "plan_started_at", "plan_status", "portal_url", "usage": {"message", "current_month": {"requests_made", "requests_left"}}}
Mappings (Business+ only)
GET /coins/mappings?coinpaprika={id} # ID mappings across providers
Query params (pass one): coinpaprika, coinmarketcap, coingecko, cryptocompare, isin, dti
Response: {"coinpaprika", "coinmarketcap", "coingecko", "cryptocompare", "isin", "dti", "updated_at"}
Changelog (Starter+ only)
GET /changelog/ids # Coin ID changes (?page, ?limit)
Response: [{"currency_id", "old_id", "new_id", "changed_at"}]
For the full OpenAPI 3.1 specification with all schemas, parameters, and response types, read references/openapi.yml. For CLI commands, read references/cli-reference.md. For the latest docs online: https://docs.coinpaprika.com/llms-full.txt
Common workflows
Get Bitcoin price (free tier, no key)
curl -s "https://api.coinpaprika.com/v1/tickers/btc-bitcoin?quotes=USD" | jq '.quotes.USD.price'
Get top 10 coins by market cap
curl -s "https://api.coinpaprika.com/v1/tickers" | jq 'sort_by(-.quotes.USD.market_cap) | .[0:10] | .[] | {name, symbol, price: .quotes.USD.price, market_cap: .quotes.USD.market_cap}'
Historical OHLCV for ETH (30 days)
curl -s "https://api.coinpaprika.com/v1/coins/eth-ethereum/ohlcv/historical?start=2025-01-01&end=2025-01-31" | jq
Search for a token
curl -s "https://api.coinpaprika.com/v1/search?q=pepe&c=currencies&limit=5" | jq '.currencies'
Look up token by contract address
curl -s "https://api.coinpaprika.com/v1/contracts/eth-ethereum/0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48" -L | jq
Note: This follows the 301 redirect automatically with -L. May need manual handling if Authorization header is required.
Get all stablecoins via tags
curl -s "https://api.coinpaprika.com/v1/tags/stablecoin?additional_fields=coins" | jq '.coins'
Returns array of coin IDs: ["usdt-tether", "usdc-usdc", "dai-dai", ...]
Convert price between currencies
curl -s "https://api.coinpaprika.com/v1/price-converter?base_currency_id=btc-bitcoin"e_currency_id=usd-us-dollars&amount=1" | jq
Common IDs
Coin IDs
Pattern: {symbol}-{name} (lowercase, hyphens for spaces)
btc-bitcoin, eth-ethereum, usdt-tether, usdc-usd-coin, bnb-binance-coin, sol-solana, xrp-xrp, ada-cardano, doge-dogecoin, dot-polkadot, avax-avalanche, matic-polygon
Platform IDs (for /contracts)
eth-ethereum, bnb-binance-coin, matic-polygon, sol-solana, arb-arbitrum, avax-avalanche, op-optimism, base-base
Exchange IDs
binance, coinbase-exchange, kraken, bybit, okx, bitfinex, kucoin
Common parameters
| Parameter | Description | Example |
|---|---|---|
quotes | Quote currencies (comma-separated) | USD,BTC,ETH |
start | Start date (RFC3339 or yyyy-mm-dd) | 2025-01-01 |
end | End date | 2025-12-31 |
interval | OHLCV: 5m, 15m, 30m, 1h, 6h, 12h, 24h. Historical tickers: 5m, 10m, 15m, 30m, 45m, 1h, 2h, 3h, 6h, 12h, 24h, 1d, 7d, 14d, 30d, 90d, 365d | 24h |
limit | Results limit | 100 |
Key response fields
Ticker
id,name,symbol,rankcirculating_supply,total_supply,max_supplyquotes.USD.price,quotes.USD.volume_24h,quotes.USD.market_capquotes.USD.percent_change_1h,percent_change_24h,percent_change_7d,percent_change_30dquotes.USD.ath_price,quotes.USD.ath_date
OHLCV
time_open,time_closeopen,high,low,closevolume,market_cap
Notes
- All timestamps are UTC. Use RFC3339 format (
2025-01-01T00:00:00Z) oryyyy-mm-dd - Coin IDs follow pattern:
{symbol}-{name}(lowercase, hyphens for spaces) - The
/tickersendpoint does NOT include tags. Use/tags/{id}?additional_fields=coinsto get coin IDs by tag. - The
/coins/{id}/twitterendpoint is deprecated and may return errors. - Global rate limit: 10 requests/second per IP.
- On 429 rate limit: Wait a few seconds/minutes, then retry. Blocks are temporary. If persistent, contact [email protected].
Related: DexPaprika
For DEX/on-chain data (pools, swaps, token prices by contract), use DexPaprika instead:
- API: https://api.dexpaprika.com (free, no key)
- Docs: https://docs.dexpaprika.com
- Agents: https://agents.dexpaprika.com
GitHub Repository
Verwandte Skills
content-collections
MetaDiese Skill bietet eine produktionsgetestete Einrichtung für Content Collections – ein TypeScript-first-Tool, das Markdown/MDX-Dateien in typsichere Datensammlungen mit Zod-Validierung umwandelt. Verwenden Sie ihn beim Erstellen von Blogs, Dokumentationsseiten oder inhaltsstarken Vite + React-Anwendungen, um Typsicherheit und automatische Inhaltsvalidierung zu gewährleisten. Er behandelt alles von der Vite-Plugin-Konfiguration und MDX-Kompilierung bis hin zur Deployment-Optimierung und Schema-Validierung.
polymarket
MetaDiese Fähigkeit ermöglicht es Entwicklern, Anwendungen mit der Polymarket-Prognosemärkte-Plattform zu erstellen, einschließlich API-Integration für Handel und Marktdaten. Sie bietet außerdem Echtzeit-Datenstreaming über WebSocket, um Live-Trades und Marktaktivitäten zu überwachen. Nutzen Sie sie zur Implementierung von Handelsstrategien oder zur Erstellung von Tools, die Live-Marktaktualisierungen verarbeiten.
creating-opencode-plugins
MetaDiese Fähigkeit unterstützt Entwickler dabei, OpenCode-Plugins zu erstellen, die in über 25 Ereignistypen wie Befehle, Dateien und LSP-Operationen eingreifen. Sie bietet die Plugin-Struktur, Event-API-Spezifikationen und Implementierungsmuster für JavaScript/TypeScript-Module. Nutzen Sie sie, wenn Sie den Lebenszyklus des OpenCode KI-Assistenten mit benutzerdefinierter ereignisgesteuerter Logik abfangen, überwachen oder erweitern müssen.
sglang
MetaSGLang ist ein hochperformantes LLM-Serving-Framework, das sich auf schnelle, strukturierte Generierung für JSON, Regex und agentenbasierte Workflows unter Verwendung seines RadixAttention-Prefix-Cachings spezialisiert. Es bietet deutlich schnellere Inferenz, insbesondere für Aufgaben mit wiederholten Präfixen, was es ideal für komplexe, strukturierte Ausgaben und Mehrfachdialoge macht. Wählen Sie SGLang gegenüber Alternativen wie vLLM, wenn Sie constrained decoding benötigen oder Anwendungen mit umfangreicher Präfix-Weitergabe entwickeln.
