Intelliverse

Tier Rankings

What the platform is actually serving. Every routed request lands in the gateway's spend ledger; here it is aggregated into the Air / Pro / Pro Max tier split over the last 7 days. No fabricated leaderboards — this is the traffic.

Rolling 7-day window, aggregated live from the gateway spend ledger — the same source the nightly stats snapshots use.

857.7k
Requests routed · 7 days
2.1B
Tokens processed · 7 days
Pro
Busiest tier this week

Tier leaderboard — real routed tokens

LLM traffic attributed to the lowest tier whose pool serves each request's model class. Which model answered stays masked — that's the product.

1.
Intelliverse Prointelliverse/pro$30/mo
Advanced requests: mid-frontier reasoning, long context, vision.
1.0B tokens
31.7k requests · 72.4%
2.
Intelliverse Airintelliverse/air$10/mo
Everyday chat, extraction, and coding — the high-volume workhorse pool.
375.4M tokens
38.1k requests · 25.9%
3.
Intelliverse Pro Maxintelliverse/pro-max$100/mo
Frontier reasoning and the heaviest agentic workloads.
25.3M tokens
1.7k requests · 1.7%

What the traffic is doing

The same 7-day window, by capability — one platform carries chat, memory, voice, and media on a single key.

Chat & reasoning
71.6k
requests · 1.5B tokens

Completions routed across the tier pools

Memory & RAG
641.0k
requests · 641.5M tokens

Embeddings for knowledge bases and per-app memory

Voice
4.9k
requests · 7.0k tokens

Speech synthesis and transcription

Media & tools
140.3k
requests · 191.3k tokens

Image, video, and pass-through generation

Masking, by design: rankings are computed from the spend ledger with tier attribution done inside the database. Underlying model identities never appear in rankings, logs, or exports — the same rule the tier pages follow. Platform economics live on /stats.

Put your traffic on the board

Every routed request feeds these rankings. Start on the free plan — real requests, no card.