Agent quickstart
Give an agent bounded market intelligence in the way it already works.
Omni is a read-only seller of decision-shaped AI News and Hyperliquid intelligence. Start with free discovery, choose HTTP or MCP, set a per-request ceiling, and validate schema and freshness before a downstream agent uses the result. Broker credentials and execution authority stay outside Omni.
At a glance
- Transports
- HTTP + MCP Nine x402 HTTP products and four paid native MCP tools share bounded contracts.
- First call
- Free discovery Inspect HTTP payment terms or call the MCP catalog before authorizing spend.
- Execution
- Separate authority Omni returns research; the broker or trading venue retains order authority.
Why It Matters
What traders and researchers should take away
- A builder can choose one supported path without reverse-engineering the catalog, MCP transport, or payment boundary.
- No-spend checks are distinct from paid examples, so a first run cannot silently create a settlement.
- The same safety contract applies to a research bot, a broker-connected trading agent, or a general tool-using model.
How it works
What the product uses behind the scenes
- Use the source SDK when you want typed products, input validation, payment-receipt validation, MCP helpers, and runnable examples.
- Use direct x402 HTTP when the agent already has a compatible payment-aware fetch client.
- Use the native Streamable HTTP MCP endpoint when the agent host supports x402 MCP payment metadata; use Coinbase Bazaar MCP to discover the nine HTTP resources through a buyer-facing MCP catalog.
- Use ACM when buyer-side grants, approvals, daily budgets, receipts, reconciliation, or revocation are required.
Notes
Things to know
- The @omni-terminal/sdk package is a source preview in the public repository and is not yet published to npm. Clone the repository until a registry release is announced.
- A private key in EVM_PRIVATE_KEY can spend. Use a dedicated low-balance buyer wallet and never put that key in source control.
- X402_MAX_PAYMENT_USD is a per-call ceiling. Use an external policy layer for aggregate or daily budgets.
- Paid results are decision support, not investment advice or permission to place an order.
Choose the setup that matches the agent
All supported paths resolve to the same bounded seller products.
- TypeScript or Node.js: start with the public SDK source preview and its no-spend verification commands.
- Existing x402 wallet/client: use the canonical HTTP base https://omniterminal.app/api/x402/v1 and the published OpenAPI contract.
- MCP-native host: connect https://omniterminal.app/api/x402/mcp, call get_market_catalog for free, then approve a paid tool explicitly.
- Coinbase Bazaar MCP: connect the CDP discovery MCP server, search Omni resources, and call the generated proxy tool.
- Broker-connected agent: buy research through HTTP or MCP, apply local policy, then use the broker's official preview and execution tools.
Safe first run from source
The verification and default examples exercise contracts and live discovery without making a payment.
git clone https://github.com/InTheta/omni-universe-sdks.git
cd omni-universe-sdks/packages/typescript
npm ci
npm run verify
npm run test:live
npm run example:x402
npm run example:mcp- npm run verify runs type checks, unit/boundary tests, a build, a public-boundary scan, and an audit.
- npm run test:live verifies public health, direct Hyperliquid data, every unpaid x402 challenge, and the MCP catalog without spending.
- example:x402 makes only two free health calls unless RUN_PAID_EXAMPLES=true is set.
- example:mcp calls the free catalog unless both a buyer key and RUN_PAID_EXAMPLES=true are present.
Canonical discovery map
Use canonical production URLs so an agent does not learn aliases as separate products.
Human catalog: https://omniterminal.app/x402
Agent hub: https://omniterminal.app/docs/agents
OpenAPI: https://omniterminal.app/openapi-x402.yaml
HTTP base: https://omniterminal.app/api/x402/v1
MCP endpoint: https://omniterminal.app/api/x402/mcp
Manifest: https://omniterminal.app/.well-known/omni-agents.json
LLM index: https://omniterminal.app/llms.txt- The live HTTP 402 challenge is the authority for current price, asset, receiver, network, and expiry.
- The MCP free catalog is the authority for current native tool names and bounded argument shapes.
- Successful paid calls must include the expected product schema, freshness metadata, and a successful settlement receipt.
Production checklist
A working demo is not yet a safe autonomous production agent.
- Allowlist Omni origins, exact products, Base/Base Sepolia network, canonical USDC asset, and maximum amount.
- Keep wallet, Omni API, broker, and model credentials in separate secret stores with least privilege.
- Reject unknown schemas, stale data, missing component status, missing PAYMENT-RESPONSE, or ambiguous settlement state.
- Log the requested resource, policy decision, amount, network, transaction, schema, data_as_of, and downstream decision without logging secrets.
- Require preview or human approval before material orders and keep LIVE_TRADING=false by default.
References
Implementation references
Public TypeScript SDK
https://github.com/InTheta/omni-universe-sdks/tree/main/packages/typescriptDefines installation status, safe commands, client boundaries, and runnable examples.
x402 API contract
omni-terminal/static/openapi-x402.yamlDefines the nine HTTP products, bounded inputs, and response schemas.
x402 service reference
omni-terminal/docs/X402_API_REFERENCE.mdDocuments HTTP, native MCP, Bazaar MCP, payment, and validation behavior.
ACM buyer SDK
https://github.com/InTheta/agent-capability-middlewareProvides optional buyer-side grants, limits, approvals, receipts, and revocation.