Turnstile or "On The List"?
Stripe shipped agent payments. The language for what agents may do was already open and free.
One strategic signal đ One people prompt đ§ One subtraction opportunity â
Created by Sam Rogers · Powered by Snap Synapse · Freely available on Substack and LinkedIn · New issue every Monday.
đ Signal: The Slot Was Already There
Stripe Sessions ran April 28-29 and shipped 288 products. Yes, the headline was real, and welcome to the future: AI agents now have payment credentials. Wallets, financial accounts, cards, embedded checkouts inside Meta and Google AI surfaces. The ceremony was probably warranted. The market just got a clean payment rail for non-human actors.
What the conference did not ship (because it was not Stripeâs job) is the language a service uses to declare what an agent may actually do once it arrives: authority, scope, approval, recourse, audit. In many ways, the credential is the easy part. The policy underneath the credential is the more important part.
That language has been drafted, in the open, for a while. Though itâs not exactly my job either, I got tired of waiting so I built this out 2-months ago. Itâs called Graceful Boundaries, an open specification any service can adopt to declare how it talks to agents. Vendor-independent. CC-BY-4.0. Free to adopt today.
Recent extension called Action Boundaries along with the first profile, Commercial Boundaries, answers the exact question Stripe Sessions opened: can a buyer agent safely understand, evaluate, transact, modify, cancel, and resolve a commercial relationship at this service.
Stripe filled the credential layer with proprietary infrastructure. The authority layer is waiting to be discovered, plainly hidden out there in the open like so many solutions these days.
đ§ Strategic (People) Prompt
Instead of asking: âHow do we add agent purchases to our checkout flow?â
Ask: âWhen an agent shows up at our service holding a Stripe-issued wallet, where does it learn what it is allowed to do, who authorized it, and what to do when an action is refused?â
If the answer is âwe will figure that out at the application layer, per integration,â that is a real gap to tend to now. Thatâs a lot of little fires to put out before they all turn into one big blaze.
â Subtraction Opportunity
Stop conflating âagent can payâ with âagent should pay.â
Payment capability is a credential layer. Authority to act is a policy layer. They may look similar at the surface but they behave very differently when something goes wrong.
The week after agent payments become real, the temptation is to bolt approval logic into the checkout flow. Resist. Approval, scope, and recourse belong in a discoverable boundary document, addressable before the agent ever hits the cart. Bolted-in approval is invisible to the agent until it fails. Discoverable approval is legible to the agent before it tries. Upstream solutions prevent downstream issues.
đȘ Analogy of the Week: The Turnstile and the List
A bouncer with a guest list is not the same entry to the club as a turnstile.
A turnstile counts as it spins. Itâs fast, mechanical, and completely indifferent. It wonât tell you whether the person passing through belongs at this event, only whether their ticket scans.
A bouncer with a guest list is slower and bossier, but the guest list is the part that matters. The list says who, under what circumstances, with what plus-ones, under whose authority, and with what recourse if there is a dispute at the door.
Stripe shipped a very fast turnstile for agents. Their turnstile looks excellent! The list, however, is still scribbled on the back of an envelope and clipped to a clipboard held by Burly T. Bouncer. Which one keeps out the riffraff and influences more spending once inside?
Some services are hoping the turnstile is sufficient. It is sufficient for Stripeâs job, which is to count cleanly and settle quickly. It is not sufficient for your job, which is to know who walked through the door and whether you want to take credit/blame for what they did once inside.
⏠Closing Notes
Open specifications win the boring layers of every infrastructure shift. Payment rails ship from one company because the economics demand it. Authority language ships from a working group because the trust does. The slot was already there. Last week it got a reason to fill up.
A list is no good if it isnât posted. The Action Boundaries document, your agents.json, your .well-known/ files: these are the artifacts an arriving agent reads to learn your door policy. Siteline.to scans for all eight categories and tells you which lines are missing, in plain language. It will not write your list for you. It will tell you whether you have a real one or not.
Until next week,
Sam Rogers
Agentic Bouncer
Snap Synapse from AI promise to AI practice
đ Book a meeting
Siteline tells you whether your list is even posted. Free scan, no signup, results in seconds. Based on Graceful Boundaries standard. Monitoring is $19/mo to keep the list watched.