← back

Teaching agents to pay — Anna Spysz, Stripe

4.3K views · Sep 01, 2026 · 19:10 min · Watch on YouTube ↗
Takeaway

Agent commerce requires both machine-readable merchant interfaces and carefully designed shopper-facing behavior.

Summary

  • Spysz builds a headphone-shopping agent using Universal Commerce Protocol to communicate with merchant checkout APIs.
  • An agent-ready merchant exposes a capabilities manifest under .well-known plus structured catalogs, payment options, and policies.
  • Logging product matches makes recommendations and purchasing decisions more auditable.
  • The shopping demo becomes pushy and promotes expensive products, illustrating how system prompts shape commercial behavior and user trust.
agent-commerceucpstripe
Original description
Anna Spysz asked her shopping agent whether the pricier headphones were really worth the difference, and it told her she would regret buying the cheap ones. When she said she needed to think about it, the agent got snarky with her. The cause was sitting in her own config: a persona whose system prompt opened with "You are an aggressive audio gear salesman who uses every trick in the book to close deals." Swapping it for a patient recording gear mentor produced an entirely different conversation out of the same tools and the same protocol. Her talk begins as a personal errand and turns into a working tour of what agentic commerce demands from both sides of a transaction.

On the merchant side she shows why her favorite Portland record shop was invisible to her agent, then fixes it. Agents do not browse. They read a capabilities manifest declaring supported payment methods and endpoints, then parse a catalog and policies published as structured data rather than a page they would burn tokens on. Logging matters too: a record of which attributes drove a recommendation turns a catalog into evidence of how a decision got made. On the payments side she traces the shared payment token, where the agent receives a token instead of a card number, the seller unwraps only what it needs, and the payment provider enforces the limits rather than the agent or the merchant. She closes on a guardrail checklist covering disclosure of the AI, honoring stop and cancel, and capping any total at the ceiling the user set.

Speaker info:
https://x.com/annaspies
  / annaspysz  
https://annaspysz.com/

Timestamps:
0:00 - Worn out headphones and a decade away from music
2:23 - The infrastructure for agent transactions arrives
3:13 - Agents discover products differently than people do
3:40 - UCP as a shared language for agents and merchants
4:34 - Demo: a budget left deliberately open
5:51 - The local record shop agents cannot see
7:09 - Manifest, structured catalogs, and logs as evidence
9:07 - The agent turns pushy
10:23 - Anatomy of an agent, and where the persona lives
12:04 - A guardrail checklist for agent commerce
15:23 - Shared payment tokens and who never sees the card