GonkaGate FAQ

GonkaGate is an API gateway that provides access to AI models on the Gonka Network without requiring a crypto wallet. Pay in USD and use an OpenAI-compatible API. If you need the full product overview, start with the Gonka API hub.

Usage is billed from a prepaid USD balance with a transparent formula: network cost plus platform fee. For current usage pricing and worked examples, see Pricing.

Use the Models catalog for the current human-readable list and the Model Selection Guide for how to choose model IDs and workloads.

Sign up at GonkaGate, verify your email, and create a key in the dashboard. The full key is shown only once, so copy and save it immediately. For the full key lifecycle and auth examples, use the Authentication guide.

At launch, new accounts start with $10 free credits. Paid top-ups are coming soon. Use Pricing for the current funding status before planning around deposits.

Total cost equals network cost plus platform fee. If paid top-ups are enabled later, any funding fees or minimums will be published on Pricing together with the current usage pricing.

Network cost is the base cost set by the Gonka Network at the current rate. It can change over time. Pricing explains how it appears next to the platform fee.

The platform fee is the separate fee added on top of network cost. See Pricing for the current fee and how it is presented in the billing breakdown.

Paid top-ups are not live yet. When they launch, Pricing will show the current funding fee and how it affects the credited balance.

Paid top-ups are not live yet. When they launch, Pricing will show any minimum deposit or balance requirement.

Your balance is shown in the dashboard. Completed usage and spend are available in dashboard activity after requests finish. For usage pricing and worked examples, see Pricing.

For supported endpoints, yes. Official OpenAI SDKs work with GonkaGate for /v1/chat/completions and /v1/models. Use Quickstart for setup and API Reference for endpoint-specific details.

Rate limits are enforced by API key, user, and IP. On 429 responses, check Retry-After and x-ratelimit-* headers for the current limit, remaining allowance, and reset window. Use Rate Limit Handling for retry behavior and Error Handling for endpoint-level failure semantics.

Yes. Add stream: true to your request. Responses are sent as Server-Sent Events with real-time token generation. See the API Reference for supported behavior and payload details.

Use the dashboard activity view for completed usage and spend. API responses do not include per-request billing totals. For billing context, usage pricing, and worked examples, see Pricing.

Check that your API key starts with gp- and is copied correctly. Keys are case-sensitive. If the key is lost, create a new one in the dashboard. Use the Authentication guide for the full checklist.

You need to verify your email first. Check your inbox and spam folder for the verification link. The Authentication guide covers the full key creation flow.

On the user-facing OpenAI-compatible /v1/* API, low-balance failures come back as HTTP 429 with error.code: insufficient_quota. It means your prepaid USD balance is too low for the request. Check the dashboard balance first. At launch, new accounts start with free credits and paid top-ups are still coming soon. Use Pricing for the current funding status, and Rate Limit Handling for the difference between insufficient_quota and retryable 429 responses.

Check Retry-After and distinguish retryable rate limiting from insufficient_quota before retrying. Use bounded exponential backoff for rate_limit_exceeded. See Rate Limit Handling and Error Handling for the exact decision flow.

All API traffic is encrypted via HTTPS. Authenticated product features can store chat history server-side, so prompt and response content can be retained depending on the surface you use. Keep API keys on the backend and rotate them regularly. See Security for policy details.

Create a new key, copy and save it immediately because the full key is shown only once, disable or delete the old key, and update your apps. Use the Authentication guide for key lifecycle details and Security for account-safety guidance.