ReferenceBeta

API reference

The OpenAI-compatible surface plus the Omnious extensions: analytics, market data, integrity, points, orders.

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

The customer-facing API is OpenAI-compatible. Use the guided section below to build an integration, then use this page as the canonical endpoint index when you need to find a specific route.

Guided API section

How the core request works

POST /v1/chat/completions works as a drop-in base_url swap for existing apps and agent frameworks, on the mainnet launch surface. Direct x402 is the default payment path: an unpaid request answers 402 Payment Requiredwith an accepts array, then the client signs and retries with PAYMENT-SIGNATURE. Invited funded keys may usex-credit-key. Payload details are in Wire formats.

Auth in the table below: pay means prepaid credit or direct x402 payment, none needs no existing credential,pub is a public read, key reads your own data via x-api-key, sig is a wallet typed-data signature, and provider is a quote signed by a registered provider key. context means the passport's bearer x-context-token, and device is the short-lived agent setup code. task means the one-time x-task-token capability (or the owning governed key). credit requires a spend-capable key and returns only requests attributed to that key. Admin surfaces (/v1/admin/*) exist but are operator-token gated and not listed here.

Canonical endpoint index

EndpointAuthPurpose
POST /v1/chat/completionspayOpenAI-compatible completions; the core paid surface
POST /v1/responsespayOpenAI Responses items and events for Codex and agent harnesses
POST /v1/messagespayAnthropic Messages compatibility for Claude Code and native clients
POST /v1/messages/count_tokenspublocal prompt-token estimate; does not start an auction
GET /v1/context/passports/:idoffNot enabled in the V1 mainnet launch
DELETE /v1/context/passports/:idoffNot enabled in the V1 mainnet launch
POST /v1/tasksnoneCreate a retained durable task and receive its capability once
GET /v1/tasks/:idtaskRead task state, latest checkpoint, approvals, and unresolved effects
GET /v1/tasks/:id/eventstaskCursor-based ordered events with bounded long polling
POST /v1/tasks/:id/claimtaskClaim or recover the task with a renewable worker lease
POST /v1/tasks/:id/checkpointstaskPersist resumable execution and context state
POST /v1/tasks/:id/effects/:effectId/begintaskWrite-ahead receipt for exactly-once side effects
DELETE /v1/tasks/:idtaskImmediately erase a task and all dependent records
POST /v1/images/generationspayPaid GPT Image generation; one image is billed per request
POST /v1/embeddingsoffNot enabled in the V1 mainnet launch
POST /v1/ordersoffNot enabled in the V1 mainnet launch
GET /healthpubrouter status, chain network, auction version
GET /v1/modelspubmodel classes with live depth and prices
POST /v1/routing/previewpubrouter-owned six-profile winners, score breakdowns, candidate counts, and data maturity
GET /v1/market/bookpubanonymized ask ladder per class
GET /v1/market/statspubrolling clearing summary (24h window)
GET /v1/market/snapshotpubfull point-in-time market snapshot
GET /v1/market/candlespubcleared-price OHLC and VWAP candles
GET /v1/market/indexpubcomposite price index and component weights
GET /v1/receipts/:idpubthe signed usage record for a request
GET /v1/analytics/requests/:idpubreconstructed auction: rivals, counterfactuals, fee split
GET /v1/auctions/latestcreditkey-scoped RFQ tape, replay, run tree, and versioned JSON
GET /v1/analytics/sessions/:idpubper-turn session tape and cache discount captured
GET /v1/analytics/marketpubper-class cleared prices, HHI, latency
GET /v1/analytics/providers/:idpuba provider's served volume and reliability
GET /v1/analytics/task-fitpubaggregate model/task quality evidence used by automatic routing
GET /v1/analytics/dashboardpubbucketed chart feed
GET /v1/analytics/leaderboardpubproviders ranked by cleared volume
GET /v1/model-integrity/claims/:idpubShadow: a provider's declared model claim; bond_amount is metadata, not escrow
GET /v1/model-integrity/challengers/:walletpubShadow: approved-reviewer status for a wallet
GET /v1/model-integrity/challenges/quoteoffShadow only; not enabled in the V1 mainnet launch
POST /v1/model-integrity/challengesoffShadow only; not enabled in the V1 mainnet launch
GET /v1/points/:walletpubmainnet Season One wallet score, tier, rank, and settled/pending earn
GET /v1/points/leaderboardpubmainnet Season One customer leaderboard
GET /v1/points/provider/:idpubmainnet Season One provider score and earn
POST /v1/points/followsigone-time 100-GPU @Omniousai follow-intent reward
POST /v1/points/demo-sharesigone-time 250-GPU Omnious demo-share intent reward
GET /v1/orders/:idpuborder state: funding, resting, filled, expired
POST /v1/orders/:id/cancelsigcancel a resting order; escrow refunds at epoch close
GET /v1/sessions/:idpubsession state and remaining budget
POST /v1/sessions/:id/closesigclose a session; unspent budget refunds
POST /v1/agent-setup/sessionsnoneStart a short-lived, wallet-bounded harness setup
GET /v1/agent-setup/sessions/:codedeviceRead the exact setup terms awaiting wallet approval
POST /v1/agent-setup/sessions/:code/approvesigApprove the displayed harness, network, budget, and expiry
POST /v1/agent-setup/tokendeviceExchange an approved device code once for its governed spend key
POST /v1/keyssigmint an API key bound to your wallet
GET /v1/keys/usagekeyper-key request and spend attribution
POST /v1/credits/depositspayfund prepaid credits with an exact on-chain USDC payment
GET /v1/credits/balancekeyread the unified API balance accessible to a spend-capable key
POST /v1/credits/withdrawalssigwithdraw prepaid credits as HyperEVM USDC to an EVM wallet
POST /v1/routing/feedback/:idstreamrecord explicit response quality using the request's stream capability
POST /provider/quotesprovidersigned standing-quote ingest (the maker side)
noteProviders do not have to speak OpenAI upstream. The router translates to Anthropic-dialect backends (/v1/messages) and back before the metering tap, so metering, billing, analytics, and the customer never know which dialect the winning backend spoke. Customers always see the OpenAI surface.

Core customer endpoints have typed methods in the SDK.