Start hereBeta

How Omnious compares

Aggregators route a call. Omnious prices it at auction and proves it with a receipt; approved-wallet integrity review remains Shadow.

Owner: Product
Version: beta-2026.07
Verified: 2026-07-13

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 and proves what happened. A limited, approved-reviewer integrity lane runs in Shadow.

Three verbs separate the two. An aggregator routes a call. Omnious lets the market price it, settles a receipt that proves it, and is testing a staked reviewer lane 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/3 auction every request, so spare, efficient capacity can win on expected cost and measured service, and peak demand surfaces as a transparently higher clear 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: a Shadow integrity market

An aggregator's quality signal is often close to “did the upstream return a 200.” Omnious additionally measures service. Shadow operator tooling can record canary evidence. Version s0-2026.07.1 also implements a points-backed challenge path for approved reviewer wallets and operator-recorded verdicts. It is Shadow, not a public bounty or USDC collateral program. 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 designed to open later. Aggregators onboard providers by hand. Omnious beta also uses allowlisted supply; permissionless onboarding is Proposed and depends on proven audit, dispute, and collateral controls. If that gate is met, the same signed quote interface can admit regional clusters and new labs. See Why sell on Omnious.

Dimension	Posted-price aggregator	Omnious
Price	Administered markup, updated by hand	Auction-cleared every request
Operator take	Spread, not itemized	Flat 7%, on every receipt
Proof	Private usage database	Signed, on-chain-anchored receipts
Quality signal	Upstream returned 200	Measured service; approved-reviewer challenge lane in Shadow
Payment	Card-first	Wallet + USDC, agent-native
Supply	Manually onboarded	Allowlisted beta; open onboarding Proposed

where an aggregator is honestly aheadSimplicity and catalog breadth are real advantages, and raw p50 latency is another: a direct route has no auction step, and Omnious optimizes for cost, proof, and quality rather than the last few milliseconds. Two of the differences above are also still maturing. The 7% fee is a real cost, not zero. And open supply is the design rather than the current state: beta runs with allowlisted providers while liquidity bootstraps. A disclosed reserve may price a winner only when there is no genuine independent rival and the reserve sample thresholds are met. Permissionless quoting remains Proposed on the roadmap. The differentiators are the mechanism, not a finished network.

As a customerIf you want one key and the widest catalog, an aggregator is the simpler tool. Reach for Omnious when you want the price discovered, the spend provable, and the quality enforced, or when your payer might be an agent rather than a person.

As a providerOn an aggregator your price is negotiated and your quality is invisible. Here your cost and measured service compete per request, and every receipt discloses what set the clear.

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