Gonka API — connect and try
Inference for agents, code and background tasks. Three paths to the network’s models — from a ready-to-use API to your own gateway.
Get a key. Connect the API.
- 01
Choose a broker
Register on its website and create an API key.
- 02
Paste the settings
Set the Base URL, that broker’s key and exact Model ID in your tool.
- 03
Run inference
Start an agent, automation or your first request.
In your familiar tools
One API for your workflows
Try a model here without registration or an API key. For your scripts, agents and background jobs, connect your chosen broker’s API.
First request example · Python
import json, os
from urllib.request import Request, urlopen
request = Request(
os.environ["GONKA_BASE_URL"] + "/chat/completions",
headers={
"Authorization": "Bearer " + os.environ["GONKA_API_KEY"],
"Content-Type": "application/json",
},
data=json.dumps({
"model": os.environ["GONKA_MODEL"],
"messages": [{"role": "user", "content": "Hello, Gonka!"}],
}).encode(),
)
with urlopen(request) as response:
print(json.load(response)["choices"][0]["message"]["content"])OpenBroker: network pricing in GNK
If you hold GNK and want to connect applications or issue keys to users, OpenBroker handles the gateway and devshards.
- 01
Create an account
Enter your organization, email and Gonka wallet address.
- 02
Deposit GNK
Send native GNK to the deposit address. The current quickstart requires at least 100 GNK to activate; check the docs for updates.
- 03
Issue a key
Create an obk- key in the dashboard once activated.
- 04
Connect your app
Set the endpoint, key and model; no gateway deployment needed.
OpenBroker documents a 0% markup: you pay for network execution, including retries. This avoids a broker markup; the total still depends on tokens and how the request runs.
OpenBroker operates the allow-listed wallet, escrows and gateway. You create the keys for your applications.
Your gateway and devshards
For operators who need their own escrow keys, session management and direct network settlement. You control and operate the infrastructure.
- 01
Governance access
The escrow creator address must be on the on-chain allowlist, updated by host governance votes. Applying does not grant access.
- 02
Your server and keys
Run a gateway on your machine, configure access and fund a dedicated GNK wallet.
- 03
Manage devshards
Open sessions, route requests, manage rotation and settle with the network.
A devshard is an inference session backed by a network deposit and request accounting. A gateway manages its lifecycle; it is neither a model nor a GPU node.
Why is access restricted?
Direct devshard access affects network operation and request accounting. While protections develop, security and stability also rely on a limited set of operators. Reputation, contributions and a clear use case help the community assess an application; governance makes the final decision.
Permissionless access is an expected direction. Current documentation sets no firm date for removing the allowlist; 2027 should not be treated as a guaranteed deadline.
Before the first request
Do I need GNK to start?
Not necessarily through an ordinary broker: payment options and bonuses depend on the service. OpenBroker and a self-hosted gateway use native GNK.
Which models are available?
The catalog changes. Copy the exact Model ID from your provider; being listed does not guarantee spare capacity right now.
Do I need a key for the demo?
No. GNK Space funds the demo. If a limit is reached or the model is unavailable, try later. Get your own broker key for use in your IDE or application.
Is this just for chat?
No. Use the API for agents, text processing and background tasks. Check broker and model support for specific features, including tool calling.