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,
as a Bearer token in the Authorization header,
or embed it in the URL path.
Get a free key from the developer portal.
Option 1 — HTTP header (recommended)
# X-Api-Key header curl -H 'X-Api-Key: YOUR_KEY' \ https://rpc.gonka.gg/chain-rpc/status # Or Bearer token curl -H 'Authorization: Bearer YOUR_KEY' \ https://rpc.gonka.gg/chain-rpc/status
Option 2 — URL path (for CLI tools)
Embed the key in the URL path: /key/YOUR_KEY/....
This is useful for tools like inferenced that cannot set custom HTTP headers.
# Key in URL path — same result, no headers needed
curl https://rpc.gonka.gg/key/YOUR_KEY/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}
Usage with inferenced CLI
The official inferenced CLI (Gonka blockchain binary) works with rpc.gonka.gg out of the box. Because the CLI cannot send custom HTTP headers, authenticate by embedding your API key in the URL path.
Node URL format
--node https://rpc.gonka.gg/key/YOUR_KEY/
The trailing slash is required. You can also use the /chain-rpc/ sub-path explicitly:
--node https://rpc.gonka.gg/key/YOUR_KEY/chain-rpc/
Examples
# Check node status inferenced status \ --node https://rpc.gonka.gg/key/YOUR_KEY/ # Query wallet balance inferenced query bank balances gonka1... \ --node https://rpc.gonka.gg/key/YOUR_KEY/ # Query all validators inferenced query staking validators \ --node https://rpc.gonka.gg/key/YOUR_KEY/ # Query a block by height inferenced query block --type=height 3468400 \ --node https://rpc.gonka.gg/key/YOUR_KEY/ # Send tokens inferenced tx bank send my-wallet gonka1... 1000ngonka \ --node https://rpc.gonka.gg/key/YOUR_KEY/ \ --chain-id gonka-mainnet \ --fees 500ngonka --yes
What works
| Category | Status | Examples |
|---|---|---|
| Node status | Full support | inferenced status |
| Bank queries | Full support | query bank balances, query bank total |
| Staking queries | Full support | query staking validators, query staking delegations |
| Gov queries | Full support | query gov proposals |
| Block / tx queries | Full support | query block, query block-results |
| Transaction broadcast | Full support | tx bank send, tx staking delegate |
| All other Cosmos modules | Full support | query auth, query authz, query ibc, etc. |
The inferenced binary can be downloaded from the
Gonka releases page.
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.