# Ed's Agentic Finance Rails > Connect AI agents to money, safely How brokers, banks and payment networks let AI agents trade, pay and manage money, and who approves what. Every fact links to a source card; unconfirmed values say "unknown". How to use it: cite the page and the source card for every fact, say "unknown" when the wiki does, and check page_status and last_verified. Warn if a page is stale or archived, or last_verified is older than 30 days. Not investment advice. Reader's guide: AGENTS.md. ## Feedback POST a short note to /feedback; instructions at /agents#giving-feedback or GET /feedback. ## Start here - [AGENTS.md](AGENTS.md): how to read and cite the wiki, and how to send corrections - [Trading](directory.md): short answer to which brokers let AI agents trade and who approves, then key fields for every broker - [FAQ](faq.md): short cited answers to common questions - [Payments](payments/README.md), [Personal money agents](personal-money/README.md), [Advisor agents](advisors/README.md), [Rails](rails/README.md): section home pages - [Approval models](approval-models/README.md): the five ways an agent's order gets approved - [What changed](changelog/README.md): every update, newest first, with the wiki in numbers - llms-full.txt (on the site): every hand-written page in one file - [providers.json](data/providers.json): the same data as JSON, with source URLs per field - [programs.json](data/programs.json): payments and personal money records as JSON, with source URLs per field - [Overview](overview.md): who lets agents in and who blocks them - [Glossary](glossary.md): short definitions of recurring terms ## Providers - [Alpaca](providers/alpaca.md): Developer-first. Hosted Trading MCP with OAuth (live and paper) plus a local open-source MCP and a CLI using API keys. No broker-side per-order approval is documented; paper trading is built in. - [Coinbase](providers/coinbase.md): Coinbase for Agents. Remote MCP with OAuth (allowlisted clients) or a local CLI with an API key. Agents can be limited to a dedicated portfolio chosen on the approval screen. - [Interactive Brokers](providers/interactive-brokers.md): Remote MCP connector. By default the AI drafts trade instructions you review and submit; eligible accounts can enable Autonomous Trading inside a separately funded AI Partition. - [Robinhood](providers/robinhood.md): Remote Trading MCP with OAuth. Agents read all Robinhood accounts but trade only in a dedicated agentic (MCP) account; per-order approval is an optional toggle. - [Webull](providers/webull.md): Two official paths. The hosted Cloud MCP prepares trade instructions that you confirm in the Webull app; the local OpenAPI MCP places orders directly, with configurable risk limits and a sandbox default. ## Payments - [Payments](payments/README.md): How AI agents pay. Card-network agent programs, payment tokens, commerce and payment protocols, and an agent credit card, each with its own page and a sourced record. - [Agentic Commerce Protocol (ACP)](payments/agentic-commerce-protocol.md): An open standard for buyers, their AI agents and businesses to complete purchases. OpenAI and Stripe maintain the spec, which is in beta. - [AP2 (Agent Payments Protocol)](payments/ap2.md): An open protocol for agent payments that records what the user authorized as signed mandates: a Checkout Mandate for the merchant and a Payment Mandate for the payment side. - [Mastercard Agent Pay](payments/mastercard-agent-pay.md): Mastercard's program for agent payments. Agents are registered and verified before they can pay, and they pay with agentic tokens. Merchants can verify agents with Web Bot Auth. - [PayPal](payments/paypal.md): PayPal offers an MCP server, run locally or hosted, and an agent toolkit that let AI agents use PayPal business APIs such as orders, invoices, subscriptions and disputes. - [Robinhood Agentic Credit Card](payments/robinhood-agentic-credit-card.md): A virtual card inside the Robinhood Gold Card that your AI agent uses through the Robinhood Banking MCP. You approve each purchase or set a required monthly limit. - [Stripe](payments/stripe.md): Stripe offers shared payment tokens, which give a seller scoped, time-limited use of a customer's payment method for agent purchases, plus an official MCP server at mcp.stripe.com. - [Visa Intelligent Commerce](payments/visa-intelligent-commerce.md): Visa's program for agent payments with Visa credentials. Approved agent builders get network-level controls, consumer-approved purchase instructions and tokenized credentials. Visa lists an MCP for it. - [x402](payments/x402.md): An open payment standard built on the HTTP 402 Payment Required status. A server asks for payment inside the web request, and the client pays and retries. Coinbase for Agents uses it. ## Personal money agents - [Personal money agents](personal-money/README.md): AI agents that work with a person's bank and card data, the tools that connect them, banks' own AI tools, and how big banks treat outside agents. - [Banks and outside agents](personal-money/banks-and-outside-agents.md): What news reports say about big US banks blocking or limiting outside AI agents, the read-only middle ground, and the US data-rights rule in the background. - [JPMorgan Smart Cash](personal-money/jpmorgan-smart-cash.md): A JPMorgan Chase AI tool in a targeted pilot. Per a news report, it aims to predict a user's cash flow and move funds to maximize yield. Only a news source is cited. - [Meta Muse](personal-money/meta-muse.md): Meta's personal AI agent. Its finance features use Plaid so people can connect bank, card, investment and mortgage accounts for personalized money guidance. - [Plaid MCP servers](personal-money/plaid.md): Plaid's MCP servers are developer tools: a hosted Dashboard MCP for production diagnostics and analytics, and a local sandbox MCP for building. They do not give agents access to end users' accounts. ## Advisor agents - [Advisor agents](advisors/README.md): AI tools that help financial advisors work with client data and firm systems. This section is new and still thin. It currently covers Claude for Financial Advisors, Nitrogen, and Wells Fargo AI Teammate. - [Claude for Financial Advisors](advisors/claude-for-financial-advisors.md): Anthropic's advisor product, with official connectors into firm systems. Official pages say Claude does not place trades or move money, and they recommend Enterprise for RIAs. - [Nitrogen](advisors/nitrogen.md): Official Nitrogen agents page documents an MCP server and approval-required actions. A Fall 2026 announcement said the suite was brought into Claude and ChatGPT and Nucleus was expanded. - [Wells Fargo AI Teammate](advisors/wells-fargo-ai-teammate.md): Official July 15, 2026 launch of a chat-based AI capability embedded in Advisor Gateway for WIM advisors, including FiNet. Later interview figures are company-reported and are labeled as such. ## Approval models - [Approval models](approval-models/README.md): The five ways brokers decide who approves an agent's order, from a walled-off account to no broker-side approval at all. - [Approval model: AI Partition](approval-models/ai-partition.md): An eligible client funds a partition inside their account where a connected AI may submit supported orders without approving each one. - [Approval model: draft, then you submit](approval-models/draft-then-submit.md): The agent writes a non-binding trade instruction; nothing happens until you review and submit it yourself in the broker's app. - [Approval model: none at the broker](approval-models/none.md): The broker executes what the agent sends. Any approval step has to live in your agent, MCP client or local server. - [Approval model: per-order confirm](approval-models/per-order-confirm.md): The agent prepares each order, and a person confirms it in the broker's own app before it reaches the market. - [Approval model: separate account](approval-models/separate-account.md): The agent can only trade in an account or portfolio you create and fund for it, so its reach is capped by what you deposit. ## Rails - [Rails](rails/README.md): The building blocks under agent access to money - how agents connect, authenticate, pay, prove who they are, and carry a user's mandate. - [Agent identity](rails/agent-identity.md): How agents can prove who they are to websites and merchants - signed HTTP requests, network-run trust protocols and proof-of-human delegation. - [Agent payments](rails/agent-payments.md): Starter overview of how agents pay - card-network agent programs, scoped payment tokens, open commerce protocols and HTTP 402 payments. - [Local MCP servers and CLIs](rails/local-mcp-and-cli.md): Self-run MCP servers and CLIs authenticate with API keys you hold, so their guardrails are only as strong as your local setup. - [Mandates and data access](rails/mandates-and-data-access.md): Protocols that record what a user authorized an agent to do, and the US data-rights rule that may shape agent access to bank data. - [Remote MCP with OAuth](rails/remote-mcp-oauth.md): How hosted broker MCP servers advertise their OAuth setup, how clients register, and why allowlisting still matters. ## Build it - [Build it](build/README.md): Practical notes for engineers and coding agents connecting to broker MCP servers safely. - [Connect an MCP client](build/connect-an-mcp-client.md): Documented connection commands and URLs for each launch broker, taken from the providers' own setup pages. - [Human-in-the-loop patterns](build/human-in-the-loop.md): Where to put human approval in an agent trading flow, and why broker-side approval beats client-side approval. - [Starter prompts for coding agents](build/starter-prompts.md): Copy-paste prompts that make a coding agent use this wiki, cite pages and say "unknown" instead of guessing. ## Comparisons - [Launch brokers compared: approval and safety posture](comparisons/launch-brokers.md): Side-by-side view of how the five launch brokers let agents trade, who approves orders, and where the guardrails are enforced. ## What changed - [What changed](changelog/README.md): Every update to the wiki, newest first, with the current size of the wiki in numbers. Generated from page headers. - [What changed: 2026-11-15](changelog/2026-11-15.md): A shorter front page, a trading-only Trading page, a cited FAQ, record tables on the Payments and Personal money pages, a What changed home page, and search and agent metadata on every page. - [What changed: 2026-11-14](changelog/2026-11-14.md): Added Payments and Personal money agents sections with one page per program, a What we cover overview on the front page, official ERC-8004, a glossary, and a front-page refresh. - [What changed: 2026-11-13](changelog/2026-11-13.md): Added a thin advisor-agents section, a third-party Schwab RIABiz source, official Coinbase agent-feedback docs, and related official and third-party source cards. - [What changed: 2026-11-12](changelog/2026-11-12.md): First draft of the wiki - five launch broker pages, 103 source cards, approval-model taxonomy and agent packaging. ## Optional - [Gaps](gaps.md): what is still unknown - [Index](index.md): every page, including all source cards - [providers.csv](data/providers.csv): CSV export