How Omnious compares

Aggregators route a call. Omnious prices it at auction, proves it with a receipt, and stakes challengers to police it — with an honest note on where aggregators lead.

Most ways to call an LLM through a third party are aggregators: they hold relationships with providers, post one price per model, and route your request to a chosen upstream. They are good at what they do, and it shows in one key, a big catalog, and low friction. Omnious is not trying to be a better aggregator. It is a different layer: a market that prices every request, proves what happened, and lets a field of challengers police the result.

Three verbs separate the two. An aggregator routes a call. Omnious lets the market price it, settles a receipt that proves it, and stakes challengers to police it. Everything below is one of those three, and each links to the mechanism that backs it.

Price: discovery, not a markup

An aggregator's prices are administered: upstream cost plus a markup, maintained by hand. They go stale, and they cannot reflect supply at this minute, whether that is idle GPUs at 3am, spot capacity, or a new entrant undercutting the field. Omnious clears a second-score auction every request, so a provider with spare hardware wins by quoting its true floor, and peak demand surfaces as a transparently higher clearing price rather than a 429. The full argument for why a live auction beats any price list is in Why a market, not a price list.

Price: one visible fee, no hidden spread

An aggregator that buys capacity at one price and resells at another keeps the spread, and you cannot see it. Omnious takes a single, flat 7% of cleared volume, with no markup on the price itself and no subscription, and that fee is receipt-verifiable: every receipt carries the cleared per-token prices and the split, and the books must reconcile to zero each epoch. It is not zero cost. It is a legible cost, and the operator earns by growing the market rather than by widening a spread. See Fees & unit economics.

Prove: on-chain receipts, not a private log

An aggregator's usage data lives in its database; you take its word for what was sent, returned, and charged. Every Omnious reply settles with a cryptographically signed receipt anchored on-chain, and /v1/analytics reconstructs the whole auction, including what each losing quote would have charged. For buyers who need an auditable spend trail (regulated finance, procurement, anyone who has to prove rather than assert), it is a buying criterion, not a nicety. The mechanics are in Tamper evidence and Receipts & analytics.

Police: quality as a market, not a status code

An aggregator's quality signal is essentially “did the upstream return a 200.” It has no cheap way to catch a provider that bids a 70B and serves a quantized 8B. Omnious turns quality into a market: approved challengers stake points against a specific receipt, an upheld challenge slashes the serving provider and pays the challenger a bounty, and one upheld substitution costs a cheat about 25 honest fills. Output quality has skin in the game, priced by people who profit from catching bad service. This is the piece an aggregator cannot copy without becoming a different kind of company. See Why verification matters and Challenges.

Two more structural differences

Wallet-native payments.The basic flow needs a wallet and USDC, not a card on file. That opens access for developers without card rails and, more importantly, for autonomous agents that must pay for their own inference without a human's card. That machine-to-machine case is one a card-first router serves awkwardly. See Paying with x402.

A supply side built to open up. Aggregators onboard providers by hand: a relationship, integration work, negotiated pricing. Omnious is designed so any provider with compute can quote into the open book, which is what lets regional clusters and new labs sell from day one and keeps competitive pressure on price. See Why sell on Omnious.

Ready to pick a door? Choose your path splits into using the market, selling into it, or reading the mechanisms end to end.