Quickstart

Your first paid completion in two minutes, from the browser or with a one-line base URL swap.

There are two doors into the market: a browser, where a wallet is created for you and the payment flow is invisible, and the API, where the same OpenAI-shaped request carries its own payment. Both end the same way: a streamed reply, a metered charge, and a signed receipt.

Path one: the browser

Open www.omnious.xyz. You need a wallet that can sign, and you get one without ceremony: a zero-config burner wallet is generated in your browser on first visit, or you can log in with email or a social account through Privy and receive an embedded wallet. Fund it with USDC (testnet USDC works against the testnet router) and ask a question.

Behind the ask, the full flow runs: the router auctions your request across every live quote, answers 402 Payment Requiredwith a worst-case price at the winner's cleared rates, your wallet signs the USDC authorization, and the reply streams back. You are charged metered actuals, not the authorized max; any overage refunds automatically. The RFQ pane shows the auction each reply cleared, and every request lands in your Activity view with its receipt.

Path two: the API

The endpoint is OpenAI-compatible: POST /v1/chat/completions with the same body and SSE stream you already send elsewhere, so pointing existing OpenAI-SDK code at the router's base URL just works for the request shape. The one addition is payment: the first POST returns a 402 quoting a signed worst case, and the retry carries an x402 PAYMENT-SIGNATURE header. The omnious-sdk client does both steps for you:

import { OmniousClient } from "omnious-sdk";

const omnious = new OmniousClient({
  routerUrl: "https://your-router.example.com",
  walletKey: process.env.OMNIOUS_WALLET_KEY, // omit on mock chains
  spendCaps: { perQueryUsd: 0.05, perDayUsd: 5 },
});

const res = await omnious.ask("Why is truthful bidding dominant?", {
  model: "qwen3-72b-instruct",
  onDelta: (d) => process.stdout.write(d),
});

Prefer a terminal? The omnious CLI speaks the same flow, and welcome gives a guided first run that checks connectivity, wallet, and next steps:

bun cli/omnious.ts welcome
bun cli/omnious.ts ask "Why is truthful bidding dominant in an Omnious auction?" --priority cheapest
bun cli/omnious.ts receipt <request-id>   # the signed usage record

The --priority flag is your first routing control: cheapest, fastest, or balanced reweight the auction score. See Routing controls for what each preset does.

What to read next

Paying with x402 explains the payment leg you just used, including why you hold only USDC and never a gas token. Receipts & analytics shows how to audit what you were charged, down to what every rival quote would have cost you instead.