Ed's Agentic Finance Rails

Approval model: none at the broker

The broker executes what the agent sends. Any approval step has to live in your agent, MCP client or local server.

Last checked

None at the broker

What it means: no broker-side approval step is documented. Guardrails, if any, are in software you control.

Examples

  • Alpaca: the CLI has no confirmation prompts and every command executes immediately.1 Paper trading is available for testing.2
  • Webull local OpenAPI MCP: places, modifies and cancels orders directly, with configurable notional limits, quantity limits and a symbol whitelist in the server you run.3

Builder notes

  • Put a human-in-the-loop step in your own client before live orders. See Human-in-the-loop patterns.
  • Start on paper or sandbox endpoints where they exist.43

Back to approval models

Sources

Suggest a correction (opens a GitHub issue)

Footnotes

  1. GitHub - alpacahq/cli: CLI for Trading API · GitHub. Alpaca (GitHub), official, retrieved 2026-11-12. ↩

  2. Alpaca - Trade with AI Using Alpaca’s MCP Server. Alpaca, official, retrieved 2026-11-12. ↩

  3. GitHub - webull-inc/webull-openapi-mcp: Webull OpenAPI MCP · GitHub. Webull (GitHub), official, retrieved 2026-11-12. ↩ ↩2

  4. GitHub - alpacahq/agentic: Multi-platform plugin marketplace for Alpaca APIs · GitHub. Alpaca (GitHub), official, retrieved 2026-11-12. ↩

Last verified 2026-11-12

Suggest a correction (GitHub issue)

Source file: approval-models/none.md

Graph View

Backlinks