The Intelliverse API is OpenAI-compatible — if your code speaks OpenAI, it already speaks Intelliverse. These docs cover everything from your first request to media generation, per-app knowledge bases, and webhooks.
curl https://router-api.intelli-verse-x.ai/v1/chat/completions \
-H "Authorization: Bearer $INTELLIVERSE_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "messages": [{ "role": "user", "content": "Say hi" }] }'Explore the docs
QuickstartCreate a key and send your first request in under a minute.API referenceChat completions, media, knowledge base, credits — request and response shapes.Migrate from OpenRouterSwap one line — the baseURL — and your existing model slugs keep working.Models & tiersThe only model strings that exist and what each plan unlocks.Rate limitsThe requests-per-minute budgets the edge actually enforces.MCP & Agent SkillsDrive the whole platform from your coding agent.
How the platform fits together
Everything hangs off two identifiers: your API key (authenticates every request, carries a plan tier) and an App ID (isolates memory, knowledge base, wallet, and channels per app or client). One flat monthly plan buys routed LLM capability; a single iv_credits balance meters media, voice, and conversation minutes on top.
- Chat —
POST /v1/chat/completions, routed at your plan's tier. See Chat completions. - Media — images, video, voiceover, music, 3D from the same key. See Media API.
- Memory — a pgvector knowledge base per App ID. See Knowledge Base.
- Channels — one normalized inbound webhook per App ID. See Channels & webhooks.
Ready to build? Start free — no card— you'll have a key and a Playground app with intro credits in about a minute.