Model aliases
You buy a plan, not a model. The model field accepts exactly five strings — the default alias intelliverse (equivalent to omitting the field), one alias per paid tier, and intelliverse/fusion for multi-model deliberation.
| Alias | Plan | Context | Requests/min | Price |
|---|---|---|---|---|
intelliverse | Free | 8,000 tokens | 10 | Free |
intelliverse/air | Intelliverse Air | 32,000 tokens | 60 | $10/mo |
intelliverse/pro | Intelliverse Pro | 128,000 tokens | 300 | $30/mo |
intelliverse/pro-max | Intelliverse Pro Max | 200,000 tokens | 1000 | $100/mo |
Note
intelliverse/air or intelliverse, but intelliverse/pro returns 403 tier_required. Fusion (intelliverse/fusion) requires Pro or Pro Max — see the Fusion guide.How routing works
Every request is classified by task (chat, coding, extraction, summarization, reasoning, RAG, vision) and routed to the cheapest option in your tier's pool that clears the quality bar for that task — with automatic failover, tuned by your app's routing profile and your workspace cost/quality slider. Responses report the tier alias as the model in all metadata.
Routing transparency
Here's exactly what masking does and doesn't cover. Model identifiers are masked in all metadata: response model fields, streaming (SSE) chunks, headers, error messages, and your logs all report the tier alias, never a provider or model name. Masking does notalter generated content — if you ask the model what it is, it may name itself in the completion text, and we don't rewrite completions. You buy routed capability at a price point, not anonymity of the text itself.
Prefer to see how each request was routed? Send the opt-in transparency header and the response carries an x-intelliverse-routing header with the task class, the tier capability pool consulted, and the cost band — never model names. Works on streaming and non-streaming responses.
curl -i https://router-api.intelli-verse-x.ai/v1/chat/completions \
-H "Authorization: Bearer $INTELLIVERSE_API_KEY" \
-H "X-Intelliverse-Transparency: routing" \
-d '{ "messages": [{"role":"user","content":"..."}] }'
# Response header (task class + tier capability pool + cost band):
# x-intelliverse-routing: {"task_class":"coding","pool":"pro/coding","cost_band":"mid"}Capability classes
Tiers unlock capability classes, not model lists. What your plan's pool must be able to do:
- Fast Chat — High-throughput conversational responses for chat and support workloads.
- Code Generation — Code completion, refactoring, and repository-scale reasoning.
- Structured Extraction — JSON-mode data extraction, classification, and transformation.
- Long Context — Documents and transcripts beyond 128k tokens.
- Frontier Reasoning — Deep multi-step reasoning for research, math, and agentic planning.
- Vision — Image understanding, OCR, chart and screenshot analysis.
- Tool Calling — Reliable function calling for agents and workflows.
- Knowledge Base (RAG) — pgvector knowledge base scoped to your App ID, grounded answers with citations.
- Fusion — Multi-model panel deliberation with a judge synthesis for maximum accuracy.
The per-tier capability matrix lives on /tiers; pricing and credit grants on /pricing.