FAQ & troubleshooting

402 loops, wallet funding, network selection, and common provider-quoter mistakes for the invite-only mainnet beta.

Owner

Developer Experience

Version

api-2026.07

Verified

2026-07-13

Short answers to the questions that actually come up, customer side first, then providers and challengers. Each answer links to the page that explains the mechanism behind it.

Why did I get a 402 error?

The recommended production path avoids this round trip: deposit prepaid credits once and send a spend-capable x-credit-key. If you call the raw endpoint without credits, it is not an error; it is the price quote. Every unpaid request answers 402 Payment Requiredwith the worst-case cost at the auction winner's cleared prices. Sign the USDC authorization and retry the same request with the PAYMENT-SIGNATURE header. The SDK does this handshake for you; if you are seeing a raw 402, you are speaking the API directly without an x402 client. See Paying with x402.

Why was I charged less than I authorized?

By design. The authorization is a worst-case ceiling; you are billed metered actuals, the tokens the router itself counted at the cleared prices. On the exact scheme the overage refunds automatically at epoch close; on the upto scheme the router settles only the actual, so there is no overage in the first place. Your receipt shows both numbers (authorized and charged).

Which network does Omnious use?

The customer product launches only on HyperEVM mainnet. The web app, docs console, SDK examples, and provider installer all default tohttps://api.omnious.xyz; there is no customer network switch.

How do I fund a wallet?

The web app's Card or bank checkout uses a region-eligible provider to buy Base USDC, then Privy bridges it into the wallet as native HyperEVM USDC. The Cryptotab shows only reviewed source-chain and asset routes and creates a route-specific deposit address after you enter the planned amount. Send exactly the chain, asset, and amount shown for that address. If you instead copy the wallet's own address, send only native HyperEVM USDC. Never reuse an archived or recovery-only deposit address. Local mock-chain routers need no key and no funds.

Do I need gas?

No. You only ever sign typed data; the router submits the transaction and pays the gas. USDC is the only asset you need on any rail.

Can providers see my prompts? Does the router store them?

The winning provider necessarily sees your prompt; it has to run the model. Ordinary completions keep receipts, not transcripts: prompt and reply bodies pass through bounded in-memory stream buffers and are swept within minutes. Explicit durable features may retain state only when enabled; Context Passports and patient orders are unavailable in the V1 mainnet launch. When enabled in a private validation environment, they retain token-protected conversation state until expiry or deletion, and an order retains a prompt until the fill before scrubbing it. See Privacy: zero retention.

What happens if the provider fails mid-stream?

You are not charged for a failed delivery: the error carries code provider_failed, and retrying re-runs the auction, most likely landing on a different provider. The failure also feeds the failing provider's measured reliability, which costs it future auctions.

Why did my quote get rejected? (providers)

The ingest gate checks four things: the TTL (valid_until must be in the future and no more than 30 seconds ahead), the signature (EIP-191 over the pipe-joined payload, by your registered key, in the exact field order), the allowlist (unknown or disabled provider ids are refused), and replay (a cancelled quote id cannot be resurrected within its TTL window). The rejection reason comes back in the response; clock skew and field-order mistakes cause most of them. See The quote book.

Why is my provider claim quarantined?

This applies to the Shadow integrity lane, not a public collateral program. An operator-recorded upheld review records the affected model claim state as quarantined. In the current Shadow mode, that state does not itself filter routing. Any points reduction is ledger accounting only; no USDC bond is escrowed. See The three verdicts and Provider bonds & quarantine.

Why can't I file a challenge against this receipt?

Public challenge access is not active. The Shadow review path is limited to approved wallets and one live review per receipt. Eligible reviewers can price the points terms first with GET /v1/model-integrity/challenges/quote; verdicts remain operator-recorded. It is not a public bounty and moves no USDC collateral.

Where do I see what rival providers would have charged?

GET /v1/analytics/requests/:idreconstructs the auction for any request: who competed, what every losing quote would have cost you, and the second-score premium. It is the receipt's companion document and it is public.