Every documented endpoint — across the edge router, knowledge base, admin/management, comms, worlds, and speech-to-text services — is described by a single machine-readable OpenAPI 3.1 document. It is generated from the actual route definitions and drift-guarded in CI, so it never falls out of sync with the API.
Interactive reference
Browse the full API — request/response schemas, auth schemes, and error responses — in the interactive explorer:
Open the interactive API reference →
Download the spec
Fetch the raw spec to generate a client SDK (openapi-generator, Speakeasy, …), import it into Postman/Insomnia, or feed it to an agent:
curl https://router.intelli-verse-x.ai/openapi.jsonThe document declares three servers (edge router-api, knowledge base router-kb, and the web app router); each operation pins the host it lives on. Authentication is described by four security schemes: the app-scoped API key (Bearer), the management key (Bearer, scoped), the internal voice s2s key header, and the channel webhook signature header.