Amex Intent Intelligence Framework: log what the agent was told

When an AI agent buys the wrong thing, the argument is about what the customer actually asked for. On October 13 American Express published its Intent Intelligence Framework, a way to capture and authenticate a shopper's instructions before an AI agent pays. Amex wants it to become an industry standard. Whether or not it does, the idea under it is one every store taking agent orders should copy now: keep a record of what the agent was allowed to do.

What actually happened

TechCrunch reports the flow has five steps:

1. A Create Intent API captures the customer's instructions and limits: merchant name, maximum budget, product preferences.
2. The customer verifies their identity and approves that captured intent.
3. Amex creates an Intent ID and a Proof of Intent Token that carries the high-level limits.
4. The token gets the agent a scoped digital payment credential. The agent never sees the real card number.
5. The Intent ID and token stay attached to the transaction for fraud checks and dispute resolution.

Amex's own example: a customer asks for white Nike sneakers in size 9, and the agent submits an order for Adidas. Amex can block that transaction because it does not match the approved intent.

The intent services are now part of the Agentic Commerce Experiences (ACE) developer toolkit Amex launched in April, per Amex's announcement. Two caveats matter. Amex gives no rollout date or merchant eligibility rules yet. And Amex told TechCrunch it has not seen disputes go up because of agentic commerce. This is built ahead of the problem, not in response to it.

Why agent purchase intent matters for your business

The chargeback is where agent commerce gets expensive for a small merchant. A customer says "my agent bought that, I didn't." Today your evidence is an order record that shows a valid card and a shipping address. That does not prove the human wanted the item.

Amex is moving the proof upstream: a signed record of what the customer authorized, attached to the payment. You do not need to wait for Amex to ship it to act on the same idea:

• Log the agent session. If an order arrives through an agent channel, store the channel, agent identifier and the cart as submitted.
• Keep the approval event. If your checkout or platform records a customer confirmation step, keep it with the order. It is dispute evidence.
• Make variant data exact. "White, size 9, Nike" only matches if your product data says white, size 9, Nike. Messy variants make mismatches look like your error.
• Tag agent orders in reporting. You cannot see if agent orders dispute more often if you cannot separate them.

Sources: TechCrunch, American Express via Business Wire.