Omni x402 Agent APIs
Seven decision-shaped products an agent can inspect and buy per request.
Omni exposes enriched AI News and Hyperliquid intelligence through the standard x402 challenge and paid-retry flow. Agents can inspect terms without an account or API key, pay only for the bounded result they need, and receive explicit freshness metadata with the response.
At a glance
- Catalog
- 7 paid routes Symbol news, market news, trader profile, liquidation map, trader leaderboard, market risk, and market snapshot.
- Access
- x402 v2 exact Unpaid requests return a discoverable 402 challenge; paid retries return bounded JSON.
- Current network
- Base Sepolia All seven templates are Bazaar-cataloged on eip155:84532. Base mainnet is implemented but not yet enabled.
Why It Matters
What traders and researchers should take away
- An agent can buy one current answer without holding an Omni subscription or long-lived API credential.
- News and liquidation context arrive as compact products rather than raw feeds that require another data pipeline.
- Freshness, scope, limits, and payment receipts give downstream automation explicit fail-closed signals.
How it works
What the product uses behind the scenes
- The canonical seller base URL is https://omniterminal.app/api/x402/v1; aliases do not create separate products.
- The gateway uses official x402 v2 middleware and CDP Bazaar discovery metadata for all seven paid route templates.
- Omni is the seller and data surface. A buyer may use any compatible x402 client; ACM is an optional buyer-side layer for grants, approvals, spend limits, receipts, and revocation.
- Successful products are allowlisted projections with schema, generated_at, data_as_of, and freshness fields.
Notes
Things to know
- The currently advertised public network is Base Sepolia testnet; do not describe Base mainnet as live until the protected CDP credential is rotated and the production gate passes.
- Paid data is decision support, not a trading outcome guarantee or execution instruction.
- The gateway never receives a buyer private key, raw trading credentials, or trading authority.
Canonical request flow
Discovery and payment use ordinary HTTP rather than a bespoke Omni protocol.
- Call a paid endpoint without a payment proof and inspect the PAYMENT-REQUIRED challenge.
- Choose an exact payment option allowed by the buyer wallet or policy layer.
- Retry with the x402 proof and require HTTP 200, PAYMENT-RESPONSE, the expected schema, and acceptable freshness.
Paid product catalog
Choose the smallest product that resolves the current agent task.
- GET /news/{symbol} or /news for enriched events, affected tickers, sentiment, impact, confidence, and market context.
- GET /trader-profile/{address}, /liquidations/{symbol}, or /traders/{symbol} for bounded Hyperliquid public-market intelligence.
- GET /market-risk/{symbol} for the joined liquidation and enriched-news proof used by the canonical ACM demo.
- GET /market-snapshot/{symbol} for bounded Hyperliquid candles plus an optional liquidation overlay.
Machine-readable contracts
The landing page, OpenAPI document, and challenge metadata serve different discovery needs.
- Use /x402 for the human catalog and pricing summary.
- Use /openapi-x402.yaml for paths, query bounds, and response schemas.
- Use the live 402 challenge as the authority for current payment terms and Bazaar metadata.
References
Implementation references
x402 API reference
omni-terminal/docs/X402_API_REFERENCE.mdDefines examples, query modes, product schemas, and buyer verification guidance.
x402 service runbook
omni-terminal/docs/X402_SERVICES.mdDocuments routing, trust boundaries, Bazaar proof, and production gates.
Public x402 OpenAPI
omni-terminal/static/openapi-x402.yamlDefines all seven canonical paid routes and their bounded contracts.