Ed's Agentic Finance Rails

Approval model: per-order confirm

The agent prepares each order, and a person confirms it in the broker's own app before it reaches the market.

Last checked

Per-order confirm

What it means: the agent can build a complete order, but the broker holds it until you confirm it in the broker’s app or website.

Examples

  • Webull Cloud MCP: each trade needs separate customer confirmation before it can be submitted.1 Every Cloud order tool is documented as needing confirmation in the Webull app or desktop.2
  • Robinhood with Trade approvals on: the agent proposes trades and you review and place them in the app. The setting is off by default for MCP accounts and still rolling out.3

Not the same as a client-side preview

A dry-run or preview inside the agent’s chat is not broker-side confirmation. Coinbase documents that Claude previews and asks before ordering while ChatGPT orders in one turn, against the same server.4 tastytrade’s MCP uses a short-lived dry-run token and states that it is not human approval.5

Back to approval models

Sources

Suggest a correction (opens a GitHub issue)

Footnotes

  1. Webull Expands Cloud MCP to Enable AI-Powered Trading Without Coding or Installation. Webull / PR Newswire, official, retrieved 2026-11-12. ↩

  2. Webull Cloud MCP Server - Webull API. Webull Developer, official, retrieved 2026-11-12. ↩

  3. Trading with your agent - Robinhood. Robinhood, official, retrieved 2026-11-12. ↩

  4. Coinbase MCP - Coinbase Developer Documentation. Coinbase Developer Platform, official, retrieved 2026-11-12. ↩

  5. GitHub - tastytrade/tastytrade-mcp: MCP server for the tastytrade open API: quotes, positions, balances, and dry-run-gated order flow for LLM agents. . tastytrade (GitHub), official, retrieved 2026-11-12. ↩

Last verified 2026-11-12

Suggest a correction (GitHub issue)

Source file: approval-models/per-order-confirm.md

Graph View

Backlinks