Kraken API
Kraken's REST and WebSocket API for spot and futures crypto trading on a regulated US-licensed exchange, using HMAC-SHA512 signed private endpoints and unauthenticated public market data feeds.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
HMAC-SHA512 is strong but shared-secret model means key exposure is catastrophic. Per-key permission scoping (query/trade/withdraw) limits blast radius. Two-factor confirmation available for withdrawals. IP allowlisting supported.
⚡ Reliability
Best When
Your agent needs a US-regulated crypto exchange with a solid compliance record, solid WebSocket v2 API, and access to both spot and futures from a single account.
Avoid When
You need maximum asset selection or the absolute lowest fees at high volume — Binance typically wins on both dimensions.
Use Cases
- • Execute spot buy/sell and stop-loss orders on a US-regulated crypto exchange with competitive fees
- • Stream real-time order book, trade, and OHLC candlestick data via WebSocket v2 for market analysis agents
- • Manage futures positions and query margin account health for automated derivatives risk agents
- • Query staking rewards and balance history for portfolio accounting and tax reporting automation
- • Implement conditional close orders (reduce-only) on Kraken Futures to automate position exit logic
Not For
- • Widest altcoin selection — Kraken lists fewer tokens than Binance; use Binance for obscure pairs
- • Institutional OTC or prime brokerage workflows — use Kraken Institutional or a prime broker
- • Automated fiat wire transfers — ACH and wire withdrawals require manual verification steps not fully automatable via API
Interface
Authentication
Private endpoints signed with HMAC-SHA512 using API key + secret. Nonce required per request (incrementing integer or timestamp). API key permissions (query, trade, deposit, withdraw) set at creation. No OAuth or JWT support.
Pricing
API access is free. Spot trading fees are volume-based. Futures fees are separate and lower. Staking and earn products have no API fee.
Agent Metadata
Known Gotchas
- ⚠ The nonce must be strictly increasing per API key — agents running concurrent requests with the same key will get EAPI:Invalid nonce errors if requests arrive out of order
- ⚠ Rate limiting uses a counter-decay system (not a fixed window) that is not directly observable; agents must implement conservative spacing to avoid hitting unpublished thresholds
- ⚠ Kraken asset names use internal identifiers (XXBT for Bitcoin, ZUSD for USD) that differ from standard tickers — agents must map between display names and API asset names via the /0/public/Assets endpoint
- ⚠ WebSocket v2 (current) and v1 (legacy) are both active but have different message schemas and auth flows — documentation sometimes mixes examples from both versions
- ⚠ Order status transitions can be delayed during high volatility; agents polling order status must handle 'open' status persisting briefly after a fill before transitioning to 'closed'
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Kraken API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.