1. Create an API key
Start free — no card (or pick a plan), then mint a key under Dashboard → Keys. Keys are shown once — copy the reveal into your password manager and export it as INTELLIVERSE_API_KEY.
2. Send your first request
Point any OpenAI client at https://router-api.intelli-verse-x.ai/v1 and authenticate with your key as a Bearer token.
curl https://router-api.intelli-verse-x.ai/v1/chat/completions \
-H "Authorization: Bearer $INTELLIVERSE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "intelliverse",
"messages": [{ "role": "user", "content": "Refactor this function..." }]
}'Note
You can omit
modelentirely — requests route at your plan's tier. The only model strings that exist are intelliverse (the default), intelliverse/air, intelliverse/pro, intelliverse/pro-max, and intelliverse/fusion. See Models & tiers.3. Read the response
Responses are standard OpenAI chat-completion objects. The model field reports your tier alias (never a provider model name), and every response carries credit headers you can meter against:
HTTP/1.1 200 OK
x-iv-credits-spent: 1
x-iv-credits-remaining: 499
{
"model": "intelliverse",
"choices": [{ "message": { "role": "assistant", "content": "..." } }]
}Next steps
- Models & tiers — what each plan unlocks and how routing decides.
- Media API — images, video, and voiceover from the same key.
- Knowledge Base — give your app grounded, cited answers.
- Migrate from OpenRouter — one-line swap, slugs keep working.