Knowledge Base Sections ▾
For Beginners
For Investors
- Where does GNK token value come from
- Gonka vs Competitors: Render, Akash, io.net
- The Libermans: from biophysics to decentralized AI
- GNK Tokenomics
- Risks and Prospects of Gonka: Objective Analysis
- Gonka vs Render Network: Detailed Comparison
- Gonka vs Akash: AI Inference vs Containers
- Gonka vs io.net: Inference vs GPU Marketplace
- Gonka vs Bittensor: A Detailed Comparison of Two Approaches to AI
- Gonka vs Flux: Two Approaches to Useful Mining
- Governance in Gonka: How a Decentralized Network is Managed
Technical
Analytics
Tools
- Cursor + Gonka AI - cheap LLM for coding
- Claude Code + Gonka AI - LLM for the terminal
- OpenClaw + Gonka AI - affordable AI agents
- OpenCode + Gonka AI - free AI for code
- Continue.dev + Gonka AI - AI for VS Code/JetBrains
- Cline + Gonka AI - AI agent in VS Code
- Aider + Gonka AI - pair programming with AI
- LangChain + Gonka AI - AI applications for pennies
- n8n + Gonka AI - automation with cheap AI
- Open WebUI + Gonka AI - your own ChatGPT
- LibreChat + Gonka AI — open-source ChatGPT
- Hermes Agent + Gonka AI — Autonomous Agent for Pennies
- Kilo Code + Gonka AI — AI-Agent in VS Code
- Roo Code + Gonka AI — Autonomous AI Agent in VS Code
- LlamaIndex + Gonka AI — RAG applications for pennies
- PydanticAI + Gonka — typed AI agents for pennies
- Vercel AI SDK + Gonka AI — AI applications in TypeScript for pennies
- TanStack AI + Gonka — AI applications in TypeScript for pennies
- API quick start — curl, Python, TypeScript
- JoinGonka Gateway — a full overview
- Management Keys — SaaS on Gonka
- Cheapest AI API: Provider Comparison 2026
- Cursor Pro request limit reached — real breakdown and cheap alternative
- Claude Code cheaper alternative — bill breakdown and switch
- Cline burned through dollars — why the agent burns money
- OpenClaw too expensive — why the agent burns tokens and how to save
- OpenRouter cheaper alternative — comparison vs JoinGonka Gateway
Tools
Roo Code + Gonka AI — Autonomous AI Agent in VS Code
Roo Code is an autonomous AI agent for VS Code: it reads and edits files, runs commands in the terminal, works with the browser, and completes multi-step development tasks. It's a fork of Cline that goes further: customizable work modes (Architect, Code, Ask, Debug, and custom), custom project-specific instructions, and a flexible model settings panel. Essentially, it's an entire team of AI specialists inside your editor.
The main problem with such agents is token consumption. For a single task, Roo Code processes file contexts, command outputs, and tool results—this can be tens of millions of tokens. At Anthropic's prices ($3-15 per 1M), one full session turns into $30-1500. For daily work, this is unrealistic.
JoinGonka Gateway reduces costs thousands of times: the same session will cost $0.01-1.00. The Gateway resells inference from the decentralized Gonka network and supports both the OpenAI format (provider "OpenAI Compatible") and the Anthropic format (endpoint /v1/messages)—Roo Code connects via either of the two. This transforms Roo Code from an expensive demonstration into a daily working tool.
Step 1: Install Roo Code and get a key
Install Roo Code: In VS Code, open Extensions (Ctrl/Cmd+Shift+X), search for “Roo Code,” and click Install. After installation, the Roo Code kangaroo icon will appear in the sidebar.
JoinGonka API key: If you don't have a key yet, register at gate.joingonka.ai/register, get 10M free tokens, and create a key with the jg- prefix in the Dashboard.
Step 2: Configure Roo Code (OpenAI Compatible)
Open the Roo Code panel and go to settings (gear icon). In the provider section, set:
- API Provider — select
OpenAI Compatible. - Base URL —
https://gate.joingonka.ai/v1 - API Key —
jg-your-key - Model (Model ID) —
Qwen/Qwen3-235B-A22B-Instruct-2507-FP8
Below, in the Model Configuration block, you can manually refine model parameters:
- Context Window —
131072(128K tokens). - Max Output Tokens —
8192for Qwen3-235B (Gateway ceiling). For Kimi K2.6, set3072; for MiniMax M2.7, set4096. - Input Price / Output Price — you can set actual rates (≈$0.0005 per 1M input, output ×3) so that Roo Code correctly calculates the cost of tasks directly in the interface.
Important about tool calling: Roo Code uses only native tool calling—there is no XML fallback like in older agents. Therefore, the model must support function calling. The default Qwen3-235B through our Gateway supports native tool calling—Roo Code works with it out of the box.
Verification: In Roo Code chat, type “Create a file hello.py with a function that prints Hello World.” The agent will suggest creating the file and show a diff for approval.
Comparing Agent Session Costs
Roo Code is an agentic tool: it doesn't respond with a single message but performs a task—reads files, writes code, runs tests, fixes bugs. Each action is a model call. Let's compare the cost of typical sessions:
| Task | Tokens | Anthropic Claude | OpenAI GPT | JoinGonka Gonka |
|---|---|---|---|---|
| Simple bug fix | ~5M | $15 — $75 | $12 — $50 | $0.005 |
| New feature (2-3 files) | ~20M | $60 — $300 | $50 — $200 | $0.02 |
| Module refactoring | ~50M | $150 — $750 | $125 — $500 | $0.05 |
| Full development session (4h) | ~100M | $300 — $1,500 | $250 — $1,000 | $0.10 |
With JoinGonka Gateway, Roo Code becomes an everyday tool—you can use it for every ticket, every bug, every feature, without worrying about the bill. 10M free tokens at startup are enough for dozens of tasks.
Model parameters (all have 128K context = 131072 tokens): Qwen3-235B — up to 8192 tokens of response; Kimi K2.6 — up to 3072; MiniMax M2.7 — up to 4096. If max_tokens for a non-stream request is not specified, the Gateway will default to returning up to 1500 tokens. Roo Code automatically breaks down long generations into steps.
How Roo Code differs from Cline: modes and Anthropic format
Roo Code is a fork of Cline, but with significant differences that change the workflow:
- Modes: Switch the agent's role to match the task—Architect for planning, Code for writing code, Ask for project questions, Debug for error searching. You can create custom modes with separate instructions and approved tool sets.
- Native tool calling only: Unlike agents with text/XML parsing, Roo Code sends tools according to the native OpenAI
toolsschema and receives calls as separate events—lower latency and more reliable results. The downside: the model must support function calling (Qwen3-235B through our Gateway supports it). - Custom instructions and profiles: Project rules (e.g., via a rules file in the repository) and several saved provider configurations that are easy to switch between.
Connecting via Anthropic format. If you want to use our /v1/messages endpoint instead of the OpenAI format: In settings, select API Provider → Anthropic, check "Use custom base URL" and specify https://gate.joingonka.ai, paste the same jg-your-key into the Anthropic API Key field, then specify the model name (e.g., Qwen/Qwen3-235B-A22B-Instruct-2507-FP8). The key and balance are shared for both formats; native tool_use in Anthropic mode also passes through the Gateway.