Omniousdocs
APIBeta

API overview

Compose a real testnet request in the Postman-style API Console, inspect its stream, headers, and receipt, then copy working code.

Owner
Developer Experience
Version
api-2026.07
Verified
2026-07-13

Omnious is an OpenAI-shaped inference API with one important difference: every paid request is priced by a live provider auction and authorized through USDC. This section is the practical path from a first read-only request to production agent traffic on HyperEVM mainnet. Direct x402 quotes and pays each request; invited funded keys remain available for approved service integrations.

optional interactive tools

Load the wallet-enabled API console only when you need it.

Start hereRead this next →Credentials, wallets, x402, and the first successful request.Chat & inferenceRead this next →Mainnet completions, streaming, tools, routing, and limits.Agent harnessesRead this next →Hermes, OpenClaw, Claude Code, and Codex — one command, one wallet-bounded key.Computer useRead this next →Pair a local CUA Driver with the SDK or an API tool loop.Market & analyticsRead this next →Public models, quotes, candles, indexes, receipts, and auction economics.Sessions & operationsRead this next →Budget sessions, API keys, credits, orders, and resumable streams.

API endpoints

NetworkBase URLUse
Mainnethttps://api.omnious.xyzProduction requests

Append the API path to the base URL, for example /v1/chat/completions. Set your SDK's routerUrl or OMNIOUS_ROUTER_URL to this mainnet base URL.

one operational integration flow

Harness selection, wallet approval, unified balance, top-up, and key management live in Integrations. These docs remain the searchable implementation reference: SDK, providers, and how it works.

the console is the quickstartUse the interactive workbench for a first request, then move the generated SDK or HTTP example into your server environment. Keep wallet signers and funded keys out of browser bundles and public repositories.

Where to go next

Start with Authentication & x402 if you are wiring a wallet, then use Chat & inference for request shapes. The wire formats page is the field-level companion to this guide.

where this lives in code