OMNITERMINAL / DOCS

Trading-agent companion

Research with Omni, then execute through the broker you already trust.

Omni is a read-only intelligence companion for agentic trading workflows. A compatible agent can use Coinbase Agentic Wallet or another x402 buyer to purchase bounded evidence, validate freshness, and then use the official Robinhood Trading MCP or another broker for account-scoped preview and execution. Omni is independent from Robinhood and Coinbase and does not receive broker credentials or trading authority.

At a glance

Discovery
HTTP + MCP All thirteen HTTP products are discoverable through Coinbase Bazaar MCP; five paid native Omni MCP tools expose standard x402 payment challenges.
Price per result
0.001–0.010 USDC The agent can inspect terms before payment and buy only the input needed for the task.
Authority
Research only Omni returns bounded data; the broker remains the system for accounts, order preview, and execution.

Why It Matters

What traders and researchers should take away

  • An equities agent can ask for fresh market-wide catalysts before it reviews a watchlist or drafts a strategy.
  • Crypto carry, liquidation pressure, public-wallet behavior, and price structure can provide cross-market context without adding a subscription.
  • Explicit schema and freshness fields let an automated workflow reject stale, malformed, or unexpectedly expensive results before acting.

How it works

What the product uses behind the scenes

  • For Coinbase Bazaar discovery, connect https://api.cdp.coinbase.com/platform/v2/x402/discovery/mcp, call search_resources, then execute a returned descriptor through proxy_tool_call.
  • Connect the Streamable HTTP MCP endpoint at https://omniterminal.app/api/x402/mcp, then call get_market_catalog without payment to inspect tools, prices, networks, markets, and allowlisted symbols.
  • For market-wide equities catalysts, call get_market_moving_events with market set to equities and omit symbol; symbol-filtered calls currently use the published crypto allowlist.
  • For HTTP clients, start at https://omniterminal.app/api/x402/v1 or use /openapi-x402.yaml; the initial unpaid response is the live authority for price and payment terms.
  • For a Robinhood Agentic account, connect https://agent.robinhood.com/mcp/trading and complete Robinhood’s desktop OAuth/onboarding flow; order placement is restricted to that dedicated Agentic account.
  • Coinbase Agentic Wallet MCP installs with npx @coinbase/payments-mcp and can discover Bazaar resources, inspect requirements, and pay an Omni HTTP route while enforcing user-owned per-call and per-session limits.
  • Keep the research and execution phases separate: validate the paid Omni result, then call the broker’s official account and trading tools under the user’s own approval policy.

Notes

Things to know

  • Omni is not affiliated with or endorsed by Robinhood; Robinhood is used here as an example of a broker-connected agent workflow.
  • The x402 result is decision support, not personalized investment advice, a return guarantee, or an instruction to trade.
  • Never send broker credentials, private keys, order authority, or non-public account data to an Omni x402 route.

Connect and discover

Start with the free MCP catalog or the public HTTP contract before authorizing any spend.

  • Add https://omniterminal.app/api/x402/mcp as a custom Streamable HTTP MCP server.
  • Call get_market_catalog and verify the expected endpoint, networks, markets, tools, prices, and response schemas.
  • Set an allowlist, per-request ceiling of 0.010 USDC, daily budget, accepted network, and freshness policy in the buyer wallet or policy layer.

Zero to one: Coinbase x402 to Robinhood Agentic Trading

Use Coinbase for bounded data payment and Robinhood for the dedicated trading account; do not share either authority with Omni.

  • Install Coinbase Agentic Wallet MCP with npx @coinbase/payments-mcp, authenticate, fund a small Base USDC balance, and set 0.010 per-call and 0.013 per-session limits.
  • Connect the official Robinhood Trading MCP at https://agent.robinhood.com/mcp/trading and complete the desktop Agentic-account setup.
  • Ask the agent to search Bazaar for Omni, inspect the Market Risk challenge, buy one 0.010 USDC result, and reject stale or incomplete evidence.
  • Use Robinhood account and market tools in read-only mode first; require a proposed order or HOLD with no submission.
  • Authorize the first real order separately with an exact symbol, side, type and immaterial maximum notional after reviewing the evidence and account scope.

Recipe: equities catalyst check

Use market-wide news to enrich a broker watchlist without handing Omni execution authority.

  • Ask: “Find fresh equities catalysts before reviewing my watchlist; summarize impact, confidence, affected tickers, and freshness.”
  • Call get_market_moving_events with market=equities, limit=5, lookback_hours=24, and event_window_minutes=60.
  • Require schema news_pulse.v1 and acceptable data_as_of/freshness values, then compare affected tickers with the watchlist inside the broker-connected agent.
  • Use the broker’s official preview and execution tools only after the user or policy layer approves the resulting strategy.

Recipe: crypto carry and liquidation check

Combine the smallest relevant Hyperliquid products instead of buying an unbounded feed.

  • Resolve ambiguous text first with resolve_market_entities when the symbol is not canonical.
  • Use get_market_carry for funding, annualized carry, open interest, premium, and mark-oracle basis.
  • Use get_market_risk_context when the decision needs joined liquidation pressure and current news catalysts.
  • Treat source status and freshness as fail-closed gates; do not infer missing data as a neutral signal.

Reusable agent prompts

Outcome-shaped prompts help a tool-using model select the right paid resource.

  • “Find today’s highest-impact equities catalysts, list affected tickers and confidence, and stop if the result is stale.”
  • “Compare BTC funding and liquidation pressure before sizing risk; spend no more than 0.004 USDC total.”
  • “Normalize these market names, then return current carry only for confidently resolved Hyperliquid symbols.”
  • “Research this public Hyperliquid wallet’s PnL, positions, and quality flags; do not place or recommend an order.”

References

Implementation references

  • Omni x402 public contract

    omni-terminal/static/openapi-x402.yaml

    Defines the thirteen HTTP resources, query bounds, prices, and successful JSON or PNG response schemas.

  • Omni x402 service runbook

    omni-terminal/docs/X402_SERVICES.md

    Documents MCP transport, payment verification, Bazaar discovery, and trust boundaries.

  • Robinhood agentic trading overview

    https://robinhood.com/us/en/support/articles/agentic-trading-overview/

    Describes Robinhood’s agentic trading model and the separation between an agent and brokerage services.

  • Robinhood trading with your agent

    https://robinhood.com/us/en/support/articles/trading-with-your-agent/

    Documents supported custom-client workflows and the broker-side trading boundary.

Next

  • Agent quickstart

    Give an agent bounded market intelligence in the way it already works.

  • Agent guide

    Research with Omni. Decide locally. Execute through one explicit account scope.

  • Omni x402 Agent APIs

    Thirteen paid products, available through HTTP and MCP.

  • Omni AI News

    A decision-ready market event stream, without rebuilding raw-news infrastructure.

  • Node + Data

    Trader-first Hyperliquid data from an owned node and orderbook stack.