What American Express shipped for agentic commerce in 2026
On 14 April 2026 American Express announced two things at once. The first is the Agentic Commerce Experiences (ACE) developer kit, a set of technical specifications for bringing Amex cards into purchases an AI agent makes for a Card Member. The second is Amex Agent Purchase Protection, which Amex calls an industry first: a commitment to back Card Member purchases made by AI agents that developers have registered with American Express.
ACE has five services. Agent registration gives each developer's agent an identity Amex recognizes. Account enablement lets a Card Member link their card to that agent, through the Amex app. Intent intelligence captures what the Card Member actually asked for. Payment credentials hands a verified agent a tokenized credential to pay with. Cart context lets the merchant share the assembled cart, which Amex says helps with disputes, and it is optional.
Amex lined up a long partner list for the launch, including Adyen, Cloudflare, Crossmint, Delta, Expedia, Fiserv, Forter, Global Payments, Google, Hilton, Microsoft, Nekuda, OpenAI, PayPal, Stripe and VGS. It also sits in Google's Agent Payments Protocol (AP2) and is a premier member of the x402 Foundation, so ACE is pitched as working alongside the open protocols rather than replacing them. Amex's own executives are candid about the stage of the market. Luke Gebb, an Amex executive vice president, told Fortune there have "probably been as many press releases as transactions" so far.
How the Amex purchase intent carries a spending amount
The detail that sets ACE apart is in the engineering write-up American Express published on 22 April 2026. An ACE intent is not a vague permission. Amex says it captures what should be purchased, where it could be purchased from, how much can be spent, and when additional approvals are required. The payment credential the agent receives is scoped, short-lived and tied to that intent, each step is validated with signed artifacts bound to the intent, and the credential has replay protection. Calls use OAuth and mutual TLS.
That is a real control, and it is more than most of the agent payment stack offers. In our earlier measurements, AWS AgentCore's whole spend policy is one optional per-session amount, and Microsoft Graph's agent types carry no money fields at all. Amex puts the amount in the authorization itself. Amex also says plainly that without a directive there is no authorization to purchase.
Notice the unit, though. The amount belongs to one intent. Amex's public materials describe nothing that totals intents across a month, compares one agent's spend against a department budget, or applies the same rule when the same agent pays with a Visa card, a Mastercard or a stablecoin wallet. A Card Member who certifies twenty intents of 400 dollars has certified 8,000 dollars, each one correctly bounded.
Is the Amex ACE developer kit public
Not yet. On 7 October 2026 we went looking for it the way an engineer would. The Amex developer portal at developer.americanexpress.com is a single-page app, and its public JavaScript bundle lists "Amex Agentic Commerce Experiences" under Payment Services, describing it as agentic commerce "powered by verified agents, real-time intent and risk signals, and robust authentication", with an overview route at /products/nextgen-agentic-payments/overview and a dedicated invite request address. The portal's product categories include an Invite-Only group.
The portal loads product pages from a public content store. The control worked. That store returned the overview for Amex's Open Banking Account and Transaction API (HTTP 200, 6,650 bytes of JSON). For the ACE product, both the overview file and the specification file returned 404, exactly what a made-up product name returned. So the ACE specification is not published where Amex publishes its other API documentation. You get it by invitation.
One trap for anyone repeating this: the developer portal answers HTTP 200 on any path, including a random one, because it is a single-page app. Requests for /mcp or /.well-known/oauth-protected-resource there look like hits and are not. That is why every probe we publish includes a nonsense control path.
Does Amex have an MCP server for agents
Not one you can reach today. The obvious names, mcp.americanexpress.com, mcp.amex.com, ace.americanexpress.com and agents.americanexpress.com, all returned NXDOMAIN on 7 October 2026, meaning they do not exist in DNS. The Amex API gateway, api.americanexpress.com, answered every MCP and OAuth discovery path with a small JSON 404, the same as our control path.
That matches what Amex wrote. Its engineering post lists SDKs, Agent Skills, an MCP server and reference implementations as tools the platform will provide. Compare Robinhood, which shipped a banking MCP server with its agentic credit card in May 2026, and Stripe, PayPal, Square and Checkout.com, which run hosted MCP servers we probed in September.
The public-facing files tell the same story. www.americanexpress.com/llms.txt exists, was last updated 18 September 2026, and contains three pieces of company trivia (the 1962 launch of a 500 dollar travelers cheque, the names of 1940s staff bowling teams, and a 1960s tuition refund program). It does not mention agents, ACE or any API. And Amex's robots.txt names exactly one crawler, AhrefsBot, and no AI crawler at all.
What Amex Agent Purchase Protection covers
The coverage rests on three conditions in the launch materials: the agent is registered with American Express, the Card Member has enrolled with that agent, and there is a certified intent for the purchase. When those hold and the agent makes a mistake, such as buying the wrong item or completing a duplicate transaction, Amex backs the Card Member. The example Amex used was an agent buying red shoes when the Card Member asked for green.
Two limits matter for a business buyer. First, the protection is for agent errors, not for errors by the Card Member or the merchant. A purchase that faithfully matches a certified intent is not an error, even if finance would never have approved it. The control is the intent you certify, so certifying broad intents is the risk. Second, the announcement materials we read publish no per-claim dollar cap, no business card terms and no claim procedure. Read the benefit terms on your own card before relying on it.
It is still a meaningful difference from the consumer competition. Robinhood's agentic credit card terms say you are solely responsible for transactions your agent makes under your instructions, which means agent purchases are treated as authorized, not as fraud.
What a finance team still has to add before agents spend on Amex
ACE answers the network's question: is this a known agent, acting for a real Card Member, inside what that person asked for. A controller has different questions, and they cut across cards.
- How much has this agent spent this month? ACE bounds each intent. Nothing in the public material totals them per agent.
- Does the same rule apply off Amex? Most companies run agents that also pay with a Visa or Mastercard virtual card, a Stripe balance or a USDC wallet for API calls. ACE governs the Amex leg only.
- Who approves above a threshold? ACE can flag that an intent needs extra approval. Routing that to a named finance approver, with an expiry, is yours to build.
- Which merchants are allowed at all? The intent says where something could be bought. A standing company allowlist across every agent is a policy, not an intent.
- What goes in the audit file at close? You need agent, amount, merchant, rule and approver in one export, matched to the card statement.
None of this is a criticism of Amex. A card network is built to authorize one transaction at a time, and ACE does that better than anyone so far. A per-agent budget is a company policy, so it lives in the company's own control plane.
How AgentsPay works alongside American Express
Keep your Amex cards, your Amex rewards and, once you have access, ACE. AgentsPay governs the agent before any card is charged. Each agent gets its own identity and wallet, a hard per-agent spend limit that totals across the month, a per-transaction ceiling, an approval threshold that pauses for a named person, and scoped virtual cards locked to the merchants you allow. Every decision lands in an audit trail you can match against your Amex statement.
The same policy applies whichever rail pays, so an agent that buys on Amex, pays an API on x402 and renews a subscription on a Visa card hits one budget, not three. The limit is a stored number checked before authorization, and the agent cannot edit its own policy.
For the other networks, see Visa Intelligent Commerce and Mastercard Agent Pay, compared side by side in Visa vs Mastercard for agents. If you are weighing a card for an agent to hold, our agentic credit card comparison covers Robinhood, Amex and business virtual cards.