API Documentation
gonka RPC exposes the full Gonka node API surface through a single base URL.
Point your app at https://rpc.gonka.gg
and you get CometBFT RPC, Cosmos REST, the Gonka API node, and fast ClickHouse-indexed history —
all through an authenticated gateway backed by a managed pool of Feather nodes with intelligent caching.
Base URL
https://rpc.gonka.gg
All paths below are relative to this base. The same URL works for every API surface — the path prefix determines what you're talking to.
Authentication
Every request requires an API key. Send it as the X-Api-Key header
or as a Bearer token in the Authorization header.
Get a free key from the developer portal.
# Header (recommended) X-Api-Key: YOUR_KEY # Or Bearer token Authorization: Bearer YOUR_KEY # curl example curl -H 'X-Api-Key: YOUR_KEY' \ https://rpc.gonka.gg/chain-rpc/status
Routing
The path prefix selects which upstream service handles your request. Requests pass through a managed Feather gateway pool with intelligent caching — immutable data (historical blocks, finalized txs) is cached 24 h, live state refreshes every 1–3 s.
| Prefix | Service | Description |
|---|---|---|
/chain-rpc/* |
CometBFT JSON-RPC | Blocks, validators, consensus, ABCI, tx broadcast |
/chain-api/* |
Cosmos REST / LCD | Bank, staking, gov, auth, IBC, CosmWasm, Gonka modules |
/v1/* |
Gonka API node | Developer-friendly JSON — models, participants, epochs, inference |
/api/ch/* |
Fast indexed data | ClickHouse-backed: tx lookup, address history, slashing, hardware, epochs |
/comet/* |
CometBFT passthrough | Direct CometBFT access (alias) |
Sending transactions
Use POST to broadcast signed transactions. Indexed data endpoints (/api/ch/*) are read-only.
Cosmos REST (recommended)
POST /chain-api/cosmos/tx/v1beta1/txs
{"tx_bytes":"...","mode":"BROADCAST_MODE_SYNC"}
CometBFT RPC
POST /chain-rpc/broadcast_tx_sync
{"jsonrpc":"2.0","method":"broadcast_tx_sync",
"params":{"tx":"0x..."},"id":1}
Endpoint reference
Search and browse every endpoint exposed by the gateway. Click a path to copy the full URL. Use the filter buttons to narrow by service, or type to search.
Errors & status codes
| Code | Meaning | Common cause |
|---|---|---|
200 | OK | Successful request |
400 | Bad request | Invalid hash, bad height, missing required param |
401 | Unauthorized | Missing or invalid API key |
403 | Forbidden | Raw ClickHouse proxy disabled, or plan limit reached |
404 | Not found | No data for the given hash/height/address |
429 | Rate limited | Too many requests — see rate limits below |
502 | Bad gateway | Upstream node (chain, scanner, ClickHouse) unavailable |
503 | Service unavailable | No healthy Feather nodes in the pool |
Rate limits
Limits are per API key. Exceed your limit and you'll receive 429 Too Many Requests.
| Plan | Requests/second | Daily limit |
|---|---|---|
| Free | 10 rps | 10,000 |
| Pro | 50 rps | 500,000 |
| Business | 200 rps | Unlimited |
Need more? See pricing or reach out at info@gonka.gg.