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 buy one bounded equities-news, crypto-news, funding, liquidation, wallet, market-structure, or risk result through HTTP or MCP, validate its freshness, and then use Robinhood or another execution venue’s own tools for order preview and execution. Omni is independent from Robinhood and does not receive broker credentials or trading authority.
At a glance
- Discovery
- HTTP + MCP Nine HTTP products and four native MCP tools expose standard x402 payment challenges.
- Price per result
- 0.001–0.003 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
- 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.
- 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.003 USDC, daily budget, accepted network, and freshness policy in the buyer wallet or policy layer.
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.yamlDefines the nine HTTP resources, query bounds, prices, and successful response schemas.
Omni x402 service runbook
omni-terminal/docs/X402_SERVICES.mdDocuments 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.