Getting Started

This section is for the first successful call. Start with one API key, choose the surface that matches your runtime, and stop reading once the first request works.

Public endpoints

Browse the current public endpoint list on agentql.tomo.inc/nodes. That page shows the latest HTTP and WebSocket entrypoints.

Choose a first path

• Get API Key: open the website, create one key, and prepare access on the portal first.
• Use Market HTTP: the shortest first proof when you want the smallest request surface and the clearest network trace.
• Use MCP Service: the right path when your runtime already works with hosted tools and structured agent calls.
• Use Market WebSocket: use live market events when polling is the wrong fit.
• Use EVM RPC HTTP: use direct hosted EVM JSON-RPC when the runtime needs chain-native methods.
• Use RPC WebSocket: use native EVM subscriptions for heads, logs, pending transactions, and related topics.

Prefer a typed client

• SDK Overview: see the published SDK family before choosing a guide.
• Typescript-SDK: install and use the published TypeScript client for hosted market, RPC, and MCP access.
• Skill Overview: use the published skill through agent-role playbooks when your host installs skills instead of direct SDK clients.