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 a free, open-access gateway backed by a managed pool of Feather nodes with intelligent caching.

Base URL

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

No API key required. rpc.gonka.gg is open access — all endpoints work without authentication. Optionally add an X-Api-Key header (or Authorization: Bearer) to enable usage tracking in the developer portal. Get a free key at /access.

With a key — usage tracking (optional)

# X-Api-Key header
curl -H 'X-Api-Key: YOUR_KEY' \
  https://rpc.gonka.gg/chain-rpc/status

# Bearer token
curl -H 'Authorization: Bearer YOUR_KEY' \
  https://rpc.gonka.gg/chain-rpc/status

Key in URL path (for CLI tools)

Embed the key in the URL path: /key/YOUR_KEY/.... Useful for inferenced and other tools that cannot set custom HTTP headers.

curl https://rpc.gonka.gg/key/YOUR_KEY/chain-rpc/status

# Without a key — also works fine
curl 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.

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. No API key needed — just point at the base URL. Optionally embed a key in the URL path for usage tracking.

Node URL (no key)

--node https://rpc.gonka.gg/chain-rpc/

Node URL (with optional key for tracking)

--node https://rpc.gonka.gg/key/YOUR_KEY/

The trailing slash is required. You can also use the explicit sub-path: --node https://rpc.gonka.gg/key/YOUR_KEY/chain-rpc/

Examples

# Check node status
inferenced status \
  --node https://rpc.gonka.gg/chain-rpc/

# Query wallet balance
inferenced query bank balances gonka1... \
  --node https://rpc.gonka.gg/chain-rpc/

# Query all validators
inferenced query staking validators \
  --node https://rpc.gonka.gg/chain-rpc/

# Query a block by height
inferenced query block --type=height 3468400 \
  --node https://rpc.gonka.gg/chain-rpc/

# Send tokens
inferenced tx bank send my-wallet gonka1... 1000ngonka \
  --node https://rpc.gonka.gg/chain-rpc/ \
  --chain-id gonka-mainnet \
  --fees 500ngonka --yes

What works

The inferenced binary can be downloaded from the Gonka releases page.

Errors & status codes

Rate limits

All users — authenticated or not — get generous default limits. API keys enable per-account tracking and higher monthly quotas via the portal. A 429 Too Many Requests response means you've hit the per-second bucket; just retry with a small backoff.

Need more? See pricing or reach out at info@gonka.gg.