JPMorgan locks AI agents out of accounts: read-only, no payments
Dimon calls outside agents 'too risky' after AI-linked breaches. Amazon already shut Meta's Muse out of retail — build for sanctioned rails, not logins.
Copy markdown
No credential logins, no moving money
Chase will not let third-party AI agents log in with customers' banking credentials; outside agents get read-only access to some account data and cannot move money or pay bills. Any agent design that drives a real Chase login is now dead at the biggest US bank — plan for read-only data plus human-approved payments.
Dimon's reason: 'thousands of rogue agents'
On the Oct 13 Q3 earnings call, Jamie Dimon called outside agents 'just too risky for clients and for JPMorgan' and warned about 'rogue agents' — 'it could be thousands of them.' The backdrop he cited: the 2025 SitusAMC vendor breach and a wave of AI-linked security incidents across the industry. Expect tighter integration reviews everywhere agents touch money.
Not just banks — Amazon already did it
Amazon blocked Meta's Muse agent from its retail site in September and earlier won a court order against Perplexity's Comet shopping bot. For anyone building agentic commerce, the two biggest targets — your customer's bank and their store — are both walling off credential and scraper-style agents. The open-web 'buy-for-me' path is closing fast.
What to build instead: sanctioned rails
Read-only aggregation still works, and for payments the permissioned path is emerging: AWS's AgentCore Payments uses the x402 '402 Payment Required' flow so agents can pay for APIs, MCP servers, and content via Stripe or Coinbase wallets, with KMS-vaulted keys the agent never sees and per-session spend caps. Design for sanctioned, auditable rails — not credential replay — if you want your agent to survive the clampdown.