API overview

The Kaonic Ai Beta API gives your product the same engine that powers the Kaonic console: adaptive question answering, African-language voice, content and marketing generation, SEO auditing, and device telemetry. One base URL, one key, JSON everywhere.

Base URL

All endpoints live under the same host that serves this documentation:

https://ai.gatavase.com/api

Requests are POST with a JSON body unless the endpoint description says otherwise. Responses are application/json; CORS is enabled for browser clients.

How authentication works

Two credential types are accepted. Pick whichever suits your integration — most server-side apps use an API key, while first-party clients use a bearer token obtained by logging in.

HeaderValueUsed for
X-Kaonic-Key GK_… (private) or KG_… (public) Server-to-server calls. Recommended.
Authorization Bearer <token or key> Clients that only support standard bearer auth.
X-Kaonic-Device-Key kai_dev_… Hardware: drones, robots, kiosks, telemetry.

Full details, including how to create and revoke keys, are on API keys & auth.

Endpoint groups

GroupEndpointsWhat it covers
Adaptive intelligence 3 Question answering, voice planning and document generation.
Content generators 7 Images, music, speech, podcasts, video prompts and transcription.
Voice, devices and verticals 6 Versioned endpoints for apps, hardware and SEO auditing.
Accounts and API keys 6 Registration, tokens, key lifecycle and usage reporting.
Business and engagement 4 Contact, careers, integrations and support data.

Credits and limits

Every account begins with 5,000 credits. Generative endpoints consume credits; the free tier allows 1,000 requests per key per day by default. When a key exceeds its daily allowance the API answers 429 rate_limited — see Errors & limits for the complete list.

Offline-first by design

Kaonic Ai Beta is built to keep working when external providers are unreachable. If a model provider is not configured, the engine answers from its own local knowledge base and deterministic templates instead of failing, so your integration degrades gracefully rather than breaking.

Next steps

  1. Quickstart — make your first request in under two minutes.
  2. API keys & auth — create, scope and revoke keys.
  3. Endpoint reference — every route with request and response shapes.