Overview
Use these guides to create one API key, make the first successful call, and then move into the exact service tree that matches your integration path.
The docs flow is intentionally task-first. Pick one surface, get one success, then move into the deeper service reference only when you need exact fields or method coverage.
Start here
Create one API key
Open Get API Key and keep Authorization: Bearer <api_key>
ready.
Pick the shortest path
Start with Call REST for the fastest hosted proof, or use Call MCP if your runtime already supports tool calls.
Drill into the exact service tree
Once the first request works, move into Services and open the matching product family or raw chain family.
Guides
Create one API key once, then reuse it across hosted MCP, REST, Market WebSocket, raw RPC, and raw RPC WebSocket.
Get API KeyFastest path to one successful hosted request.
Call RESTHosted tool-style access for agent runtimes.
Call MCPProduct-level market streaming with one hosted socket.
Call Market WebSocketRaw EVM family and Solana (Beta) JSON-RPC access.
Call RPCNative chain subscriptions under hosted websocket routes.
Call RPC WebSocketCurrent public endpoints
- Gateway base URL:
https://gw-aql.tomo.services - Hosted MCP URL:
https://mcp-aql.tomo.services - Market WebSocket URL:
wss://gw-aql.tomo.services/v1/market/ws
Browse by service family
Canonical market reads for profile, price, liquidity context, and OHLCV.
Market APIProduct-level stream pages for connect, price, OHLCV, and status events.
Market WebSocketThe current hosted EVM route family across the raw RPC baseline.
EVMHosted Solana raw routes and subscriptions with a clear Beta label.
Solana (Beta)