For AI Agents — gonka RPC

Machine-readable discovery files

We serve standard llms.txt files that AI agents check automatically when they need to understand a service. No configuration needed — just point the agent at rpc.gonka.gg and it will find everything.

/llms.txt — Quick overview /llms-full.txt — Full 352-endpoint reference /api/endpoints — Structured JSON catalog

Cursor / Windsurf / Cline

Add this to your project's rules file (.cursorrules, .windsurfrules, or AGENTS.md) so your coding agent knows about gonka RPC:

# Gonka blockchain RPC

When interacting with the Gonka blockchain, use the gonka RPC service:
- Base URL: https://rpc.gonka.gg
- Auth: send header X-Api-Key: YOUR_KEY on every request
- Full API reference: https://rpc.gonka.gg/llms-full.txt
- Quick overview: https://rpc.gonka.gg/llms.txt
- JSON catalog: https://rpc.gonka.gg/api/endpoints

Key routing prefixes:
  /chain-rpc/*  → CometBFT JSON-RPC (blocks, validators, consensus)
  /chain-api/*  → Cosmos REST (bank, staking, gov, IBC, CosmWasm)
  /v1/*         → Gonka API (models, inference, participants, training)
  /api/ch/*     → Fast indexed data (tx lookup, address history, hardware)

Fetch /llms-full.txt for the complete endpoint list before writing code.

Tip: With this rule in place, you can just say "query the latest gonka block" or "check validator set" — the agent will know which endpoint to call and how to authenticate.

Custom GPTs / OpenAI Assistants

Add this to the system prompt of your GPT or Assistant:

# System prompt addition:

You can interact with the Gonka blockchain via rpc.gonka.gg.
Auth: include header X-Api-Key with value YOUR_KEY.
To discover available endpoints, fetch:
  https://rpc.gonka.gg/api/endpoints (JSON)
  https://rpc.gonka.gg/llms-full.txt (text)

Use the JSON catalog to find the right endpoint, then make
the HTTP request on behalf of the user.

Using the JSON catalog as a tool

If your GPT supports function calling, you can register a tool that fetches GET https://rpc.gonka.gg/api/endpoints to dynamically discover endpoints filtered by group, method, or keyword. The response includes structured metadata for every endpoint: method, path, description, parameters, and cache TTL.

OpenClaw / Autonomous agents

For fully autonomous agents (OpenClaw bots, LangChain agents, AutoGPT, etc.), the recommended flow is:

Fetch https://rpc.gonka.gg/llms.txt for quick context (auth, routing, key examples)
If more detail is needed, fetch https://rpc.gonka.gg/llms-full.txt for the complete endpoint reference
Or use GET /api/endpoints (JSON) for programmatic filtering
Include the X-Api-Key header on every API request

# Example: Python agent discovering endpoints
import requests

# 1. Discover what's available
catalog = requests.get(
    "https://rpc.gonka.gg/api/endpoints"
).json()

# 2. Find the endpoint you need
for group in catalog["groups"]:
    for ep in group["endpoints"]:
        if "validator" in ep["description"].lower():
            print(f'{ep["method"]} {ep["path"]} — {ep["description"]}')

# 3. Call it
resp = requests.get(
    "https://rpc.gonka.gg/chain-api/cosmos/staking/v1beta1/validators",
    headers={"X-Api-Key": "YOUR_KEY"}
)
print(resp.json())

What your agent can do

Query blockchain state — blocks, transactions, account balances, validators, governance proposals
Search transactions — by hash, by address history, by event filters, across full chain history
Monitor validators — signing info, slashing events, delegations, commission
Submit transactions — broadcast signed txs via CometBFT RPC or Cosmos REST
Run AI inference — call the OpenAI-compatible /v1/chat/completions endpoint
Access indexed analytics — fast ClickHouse-powered lookups for tx history, hardware nodes, epoch performance
Manage training tasks — create, list, and monitor distributed training jobs
Interact with IBC / CosmWasm — query IBC channels, smart contracts, denom traces

Example conversations

User: "Check the latest gonka block"

Agent fetches GET /chain-rpc/block → returns the latest block header, hash, height, timestamp, and transaction count.

User: "How many tokens does gonka1abc...xyz hold?"

Agent fetches GET /chain-api/cosmos/bank/v1beta1/balances/gonka1abc...xyz → returns all token balances for the address.

User: "Show me the last 20 transactions for this address"

Agent fetches GET /api/ch/address/{address}?limit=20 → returns paginated transaction history from the indexed database, newest first.

User: "What AI models are available on gonka?"

Agent fetches GET /v1/models → returns all registered AI models with their capacities and pricing.

User: "Monitor node slashing events from the last 1000 blocks"

Agent fetches GET /api/ch/slashing?from_height={current-1000}&limit=50 → returns recent slashing events, filterable by validator.

Need an API key? Get started free → · Full endpoint docs: API reference → · Questions? info@gonka.gg