Limits & Quotas

Gonka Broker enforces safety limits to protect you from accidental overspending, runaway scripts, and other unexpected situations. These limits are designed to keep you safe, not to restrict normal usage.

Payment limits

Every top-up is checked against three safety limits:

• Minimum per payment: prevents accidentally tiny charges that would mostly go to payment processing fees.
• Maximum per payment: prevents typos like adding an extra zero and paying $10,000 instead of $1,000.
• Maximum per 24 hours: caps total spending within a rolling 24-hour window, protecting against payment loops or other unexpected behavior.

These limits are system-wide defaults. If a payment exceeds any of them, it will be declined and you will see an error message with the specific limit.

API key limits

There is a maximum number of API keys per account. This encourages good key hygiene: if you need a fresh key, rotate your existing one instead of creating a new key.

The default limit applies to all accounts. If you genuinely need more keys, contact us at info@gonkabroker.com and we can adjust the limit for your account.

Rate limits

API requests are rate-limited on a per-key basis (requests per minute). As the network grows, this limit is continuously increased. You can check the current RPM limit for your key by calling the GET /test-auth endpoint:

curl https://proxy.gonkabroker.com/test-auth \
  -H "Authorization: Bearer YOUR_API_KEY"

The response includes your key’s maxRpm value in the settings object.

If you need a higher RPM, contact us at info@gonkabroker.com; limits can be adjusted per key.

Free-tier rate limit

If a free tier is available on your account and it is running on free-tier funds only, requests are capped at a lower rate; the current cap is visible as maxRpm in the /test-auth response above. Hitting the cap returns 429 with a rate_limit_error message explaining the limit. The cap is lifted within about a minute after a top-up. See Billing & Deposits for how the free tier works.

When your balance runs out

With no remaining balance at all, the API stops accepting new requests and returns 429 with the code insufficient_quota:

{
  "error": {
    "message": "Balance exhausted. Top up to continue: ...",
    "type": "insufficient_quota",
    "param": null,
    "code": "insufficient_quota"
  }
}

Top up to resume; the block is lifted within about a minute.