kraken.com valid

Kraken Developers

Kraken provides APIs for three distinct platforms: Exchange (Spot and Derivatives trading), Institutional (OTC, custody, prime brokerage), and Embed (B2B white-label integration).

For agents: Kraken developer hub for Exchange (spot and derivatives trading), Institutional (OTC, custody, prime brokerage) and Embed white-label APIs.

crypto exchange apispot tradingderivativesotc tradingcustody

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T13:14:15.656Z. Cached copy · Source on kraken.com

# Kraken Developers

Kraken provides APIs for three distinct platforms: Exchange (Spot and Derivatives trading), Institutional (OTC, custody, prime brokerage), and Embed (B2B white-label integration).

## Exchange

Spot and Derivatives trading via REST, WebSocket, and FIX 4.4.

- Spot REST: https://api.kraken.com — market data, order entry, account management, funding, Earn
- Affiliate REST: https://api.kraken.com — referred-user activity, CPA progress, and payout history for approved KOL partners (`GET /affiliate/v1/daily-activity`, `GET /affiliate/v1/cpa-progress`, `GET /affiliate/v1/payout-history`)
- Spot WebSocket v2 (recommended): wss://ws.kraken.com/v2 — real-time channels: book, ticker, trade, executions, balances, level3
- Spot WebSocket v1 (legacy): wss://ws.kraken.com
- Derivatives REST: https://futures.kraken.com/derivatives/api/v3
- Derivatives WebSocket (streaming only): wss://futures.kraken.com/ws/v1
- Unified FIX 4.4: colo-london.vip-ws.kraken.com — covers both Spot and Derivatives in one session

Authentication: Spot REST uses HMAC-SHA512 (API-Key + API-Sign headers). WebSocket uses a token obtained from GetWebSocketsToken REST endpoint. FIX uses SenderCompID + password in Logon message. Derivatives REST uses APIKey + Authent headers (HMAC-SHA512 via SHA256 intermediate hash).

Key concepts: cl_ord_id (client order identifiers), atomic amends (in-place order modification), cancel-on-disconnect (FIX only), L3 market data (individual orders in book), CRC32 checksums for book validation.

Rate limits: Spot REST has a call counter (max 15-20 depending on tier). Trading engine has per-pair counters with decay. Derivatives has cost-per-request budget (500/10s).

Colocation: Direct cross-connect at Equinix London (~200μs). Beeks Financial Cloud (~200μs). AWS London (~2ms).

## Institutional

APIs for institutions managing large positions or client assets.

- Custody REST: digital asset custody, deposits, withdrawals
- OTC REST: block trade execution off the order book
- Prime FIX: institutional FIX connectivity for order management
- Prime WebSocket: real-time streaming for prime brokerage

Access requires onboarding through a Kraken Account Manager.

## Embed

B2B APIs for integrating Kraken financial infrastructure into third-party products under their own brand.

- Embed REST: white-label trading and account management
- Ramp REST: fiat on-ramp and off-ramp
- Pay REST: crypto payment acceptance and sending
- OAuth REST: OAuth 2.0 authorization on behalf of Kraken users

Access requires B2B partner approval.

## Developer tooling

### kraken-cli
A compiled binary CLI (no runtime dependencies) for Spot and Derivatives trading from the terminal. Written in Rust.
- 151 commands across REST, WebSocket, and account management
- Covers: Spot REST, Derivatives REST, Spot WebSocket v2, Derivatives WebSocket v1, L3 order book
- Paper trading: test strategies against live prices without auth or capital (spot and futures)
- Built-in MCP server:
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=kraken.com · GET /v1/domain/kraken.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for kraken.com:
1. POST https://agentwebmap.com/v1/sites/kraken.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://kraken.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/kraken.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/kraken.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.