Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.kallglot.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Rate Limits

Throughput limits guard the shared API; billing is enforced separately via API credits.
A request may return 429 (rate limit) or 402 insufficient_api_credits (credits). Treat them differently: wait and retry vs top up credits.
Numeric plan tiers below are examples only. What matters for production is what your Dashboard / account shows plus the X-RateLimit-* headers on live responses (X-RateLimit-Reset is authoritative for window timing).

​
Example tiers (non-binding)

Plan (example)HTTP volume (idea)Concurrent sessions (idea)
Test / Startertens–hundreds RPMsmall integer
Prohigher RPMlarger
EnterpriseCustom — set in contractCustom
For exact quotas, negotiate with Kallglot or read your provisioning email / portal—not this table.

​
Response headers

Responses may include throughput and billing hints: 
HTTP/1.1 200 OK
X-RateLimit-Limit: 120
X-RateLimit-Remaining: 118
X-RateLimit-Reset: 1711454460
X-API-Credits-Remaining: 412
X-API-Credits-Used: 588
HeaderHow to use it
X-RateLimit-RemainingSlow down proactively when low
X-RateLimit-ResetSleep until Unix time if you blew the window
X-API-Credits-*Drive dashboards / alerts

​
Too many requests (429)

{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "You have exceeded the rate limit. Please retry after 30 seconds.",
    "type": "rate_limit_error"
  }
}
Honor Retry-After (seconds). Back off exponentially if you burst repeatedly. 
async function fetchWithBackoff(url, init, attempts = 4) {
  for (let i = 0; i < attempts; i++) {
    const response = await fetch(url, init);
    if (response.status !== 429) {
      return response;
    }
    const retryAfterSec = Number(response.headers.get('Retry-After') || '30');
    await new Promise(resolve => setTimeout(resolve, retryAfterSec * 1000));
  }
  throw new Error('Rate limited after retries');
}

​
Out of credits (402)

{
  "error": {
    "code": "insufficient_api_credits",
    "message": "API credits exhausted. Purchase more credits to continue.",
    "type": "permission_error"
  }
}
No amount of backoff fixes this—increase quota in the Developer Portal or contact support.

​
Integration habits

DoWhy
Cache GET /v1/sessions/{id} per id for a short TTLFewer redundant reads
Prefer webhooks for lifecycle vs tight polling loopsSaves HTTP budget
Keep one slow consumer queue for POST …/analysisAnalysis is heavier than ordinary CRUD
Re-create sessions sparingly after dropsCreation endpoints are often the hottest
There is no GET /v1/sessions list API — retain session ids (sess_…) from POST /v1/sessions, redirects, or webhooks.

​
Need higher limits?