Overview

Start with one API key, choose one transport, then open the exact service or method page you need.

Public entry points

Get API Key: create one key on the website, then reuse it across HTTP, MCP, WebSocket, and EVM RPC.
Use Market HTTP: the shortest path to one successful hosted request with a visible network trace.
Use MCP Service: use the hosted MCP endpoint when your runtime already works with tools and agent calls.
Use Market WebSocket: start with live price or OHLCV events instead of polling.
Use EVM RPC HTTP: use native EVM JSON-RPC when you need chain-level methods instead of normalized market reads.
Use Typescript-SDK: start with the published typed client if your stack already uses TypeScript or modern JavaScript.
Use Skill Playbooks: start from installable agent-role guides if your host consumes skills instead of direct transport code.

Market API: canonical HTTP reads for price snapshot, OHLCV, asset profile, and market profile.
Market WebSocket: product-level stream docs for connect, price streams, OHLCV streams, and status events.
EVM RPC: hosted EVM raw-route family across HTTP API and WebSocket API entry points.
Solana (Beta): compatibility reference pages for the current beta surface.

Getting Started: task-first onboarding pages for the first successful call.
Use Cases: common jobs such as latest price lookup, live price boards, OHLCV charts, market checks, and native EVM subscriptions.
Services: product-family and chain-family directory for all public API references.
SDK: typed client entrypoints aligned with the same hosted route truth as the raw transport examples.
Skill: installable skill guidance organized by agent role rather than by transport.