Omni x402 Agent APIs
Thirteen paid products, available through HTTP and MCP.
Omni exposes equities/crypto AI News and Hyperliquid intelligence through the standard x402 challenge and paid-retry flow. Agents can use bounded HTTP products or Streamable HTTP MCP tools, inspect terms without an account or API key, and receive explicit freshness metadata with the paid result.
At a glance
- Catalog
- 13 routes + MCP Ten JSON routes, three PNG routes, plus five paid native MCP research tools.
- Access
- x402 v2 exact Unpaid requests return a discoverable 402 challenge; paid retries return bounded JSON.
- Current network
- Base + Sepolia All thirteen advertise eip155:84532 and guarded eip155:8453, and all thirteen are funded and Bazaar-indexed.
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
- Start at /docs/agents for the setup matrix, then use /docs/typescript-sdk or the dedicated HTTP and MCP guides for copyable examples.
- 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 thirteen paid route templates.
- The Streamable HTTP MCP endpoint is https://omniterminal.app/api/x402/mcp and uses the official @x402/mcp payment wrapper.
- 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
- Base Sepolia remains the Bazaar registration network; guarded Base mainnet is also advertised for exact canonical-USDC payment.
- 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 standard HTTP or MCP transport rather than a bespoke Omni protocol.
- Call a paid endpoint without a payment proof and inspect the PAYMENT-REQUIRED challenge.
- MCP clients can call get_market_catalog for free, then use paid News, Market Risk, Entity Resolution, Market Carry, or Pre-Market Roundup tools through the same x402 boundary.
- 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. Liquidation responses include every bounded published long/short position level, the resulting sell/buy flow, distance from the live Hyperliquid mark price, and ±1/2/5/10% public-market stress scenarios.
- GET /market-risk/{symbol} for joined liquidation levels, margin stress, current funding, and enriched news used by the canonical ACM demo.
- GET /market-snapshot/{symbol} for bounded Hyperliquid candles, current funding, and an optional all-level liquidation and margin-stress overlay.
- POST /symbols/resolve for current-only canonical instrument resolution, GET /market-carry/{symbol} for current hourly funding with mechanical 8h, 1d, and APR projections, or GET /research/premarket for Omni’s latest published morning thesis; add date=YYYY-MM-DD for an exact publication date.
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 /api/x402/mcp for stateless Streamable HTTP MCP discovery and tool calls.
- 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 thirteen canonical paid routes and their bounded JSON or PNG contracts.