Case studyBuild2026
Okay-Pay
TL;DR
Letting an AI shopping agent spend only on what you meant.
- Problem: Agent payment protocols (Google's AP2 and Mastercard's Verifiable Intent) enforce amount, store and product ID, but not what shoppers actually say: "waterproof", "free returns", "ask me if it's over $80". The agent writes even those 3 itself, so they can drift: one model wrote brooks.com for the Brooks store (brooksrunning.com)
- Approach: a flow where the AI recommends, the shopper chooses, and code decides, with PayPal holding the money until every rule passes
- Evidence: every AI step chosen by eval: 0 critical errors in 117 drafter runs, and a $100 prompt-injection attack cut to $0
- Of 10 things people tell a shopping agent, the protocols enforce 3 (how much, where, what by product ID). Okay-Pay adds 4 (must-haves, substitutes, check-ins, conditions of sale), and 3 stay open (when, who it's for, values)

