Rpc Gg

Thin proxy for the gonka chain at https://rpc.gonka.gg. Supply any REST/JSON-RPC path (CometBFT /chain-rpc/*, Cosmos LCD /chain-api/*, Gonka modules /chain-api/productscience/*, API-node /v1/*, or the fast indexer /api/ch/*) and the block forwards your call with the X-Api-Key header pulled from your saved secret. Returns the response body (parsed JSON when possible) plus the HTTP status. See https://rpc.gonka.gg/llms-full.txt for the full 354-endpoint reference.

jobwebv0.2.1Featured
Updated 41d ago · 3 total runs

Inputs

api_keysecretrequiredGonka RPC API key. Save it once on the Secrets page as API_KEY (or map a different saved secret below). Sent as X-Api-Key on every request.
pathstringrequiredEndpoint path — e.g. "/api/ch/blocks/latest", "/v1/status", "/chain-api/cosmos/bank/v1beta1/supply". Leading slash optional; https://rpc.gonka.gg is prepended automatically. Supports {arg} for a single dynamic segment (see path_arg) or {name} placeholders filled from path_params — useful when a segment comes from an upstream node, e.g. "/chain-api/productscience/inference/inference/epoch_group_data/{arg}".
path_argstringConvenience scalar. Substituted for {arg} in path. Makes dynamic URL segments trivial to wire from an upstream node — no string building needed. Example path "/…/epoch_group_data/{arg}" + path_arg "238" → "/…/epoch_group_data/238".
path_paramsstringOptional JSON object of named path substitutions — e.g. {"epoch": 238, "participantId": "gonka1…"} fills {epoch} and {participantId} placeholders in path. Use this for endpoints with multiple dynamic segments. If you accidentally wire a plain scalar here instead of path_arg, it is auto-promoted to path_arg.
methodstringHTTP method. Most read endpoints are GET; broadcast_tx_* and a handful of others are POST.
querystringOptional query string or JSON object of params. Strings pass through verbatim ("height=3397529&prove=false"); JSON ({"limit":10}) gets URL-encoded for you.
bodystringRequest body for POST calls. Typically a JSON string. Empty for GETs.
timeout_secondsintegerHTTP timeout in seconds. Gonka caches most endpoints for 1–30s so 30s is plenty.

Outputs

statusinteger
okboolean
urlstring
content_typestring
body_textstring
jsonjson
errorstring

Resources

CPU
0.5
Memory
256 MB
Timeout
180s