CryptoGrindCryptoGrindDocs
Open Dashboard

Getting started

Authentication

Two ways in: a subscription API key (for keyed access at your tier) or x402 pay-per-call (anonymous, request/response only).

API keys

Keys are issued from your profile once you hold a machine-API plan. Pass the key in the apikey header on every request:

bash
curl -H "apikey: $CRYPTOGRIND_KEY" \
  "https://api.cryptogrindtrade.com/v1/prices/latest?exchange=binance&symbol=BTC_USDT"

For WebSocket, supply the key via your client's header support (the gateway authenticates the upgrade). Your tier and rate limit are derived from the key — see Access tiers.

Keep keys server-side

A key carries your tier and quota. Never ship it in browser or mobile client code — proxy requests through your backend. Rotate or revoke compromised keys from the API-keys tab.

x402 pay-per-call

A subset of REST endpoints (delayed snapshots, history pages, the funding board, splash history) accept x402 micropayments — no account, no key, payment is the auth. An unpaid request returns 402 Payment Required with payment instructions; pay (USDC on Base) and retry.

x402 is request/response only — it never covers live WebSocket streams. For live data, use a keyed plan.

Consumer identity

Behind the gateway, every request resolves to a consumer (your key or x402 wallet). Responses include a trace watermark unique to your consumer — useful for support and abuse tracing.