Gonka · Developer infrastructure

One gateway. Six ways to reach chain and index data.

RPC.gg fronts Feather nodes and the tx-scanner stack behind a single origin—like Infura for Ethereum, tuned for Gonka: JSON-RPC, Cosmos REST, indexed HTTP, safe read-only index APIs, optional direct Comet, and a portal for keys.

Chain RPC

Tendermint / CometBFT JSON-RPC

Wallets, CosmJS, and backends send abci_query, tx, block, and status calls through the gateway with load-balanced upstreams.

Same paths as upstream Feather
Stable base URL for production
Prefix /chain-rpc/

See example URL

LCD / REST

Cosmos gRPC-gateway paths

REST clients and explorers hit LCD-style routes—bank, staking, auth—without talking to nodes directly.

Compatible with standard Cosmos REST
Prefix /chain-api/

See example URL

Tx index

Tx-scanner HTTP API

Search and health endpoints from the hosted scanner—proxied at /index/ when the service is wired to your deployment.

ClickHouse-backed index upstream
Prefix /index/api/v1/

See example URL

Safe ClickHouse

Server-built JSON only

GET /api/ch/* returns transactions, blocks, addresses, slashing, hardware, and epoch stats using fixed, validated queries—no ad hoc SQL from clients.

Validated paths and query params
Row counts for indexed tables below

Browse API reference

Comet RPC

Direct node RPC passthrough

Optional /comet/ forwards to CometBFT HTTP when we expose it for your project—useful for low-level RPC outside the Feather pool.

Same paths as native :26657

See example URL

Portal & keys

GG Wallet sign-in

With auth enabled, send X-Api-Key or Bearer tokens on protected routes. Mint keys in the portal after wallet login.

Public: /health, UI pages, status JSON
Protected: chain, index, index JSON APIs, comet

Get access

Index volume (ClickHouse)

Approximate row counts across the indexed datasets we serve via GET /api/ch/*. Figures are cached briefly and skipped when the index backend is not configured.