Websites increasingly decide whether an AI agent may book and pay, so tune your purchasing rules to match.
Why this is useful to know
AI agents are increasingly booking, paying and cancelling subscriptions on their own. Nate Jones shows that this already runs into walls. A hotel can block the booking, even if your agent planned the trip perfectly. So the problem is not just the model, but also the website the agent has to use. Soon, businesses will choose per site: a fixed, recognisable route for agents, the regular website, or nothing at all. For you, this means you are not only choosing which assistant you use, but also which suppliers it can still reach. That is worth knowing, because it decides where your money goes.
When you need this
You run into this when your agent gets stuck on a payment page. Then you have two choices: complete the payment yourself, or pick a supplier your agent can use. Start small. Give the agent only the accounts and the amount it needs for one task. Approve every purchase, cancellation or payment yourself in advance. Check the result where it is supposed to arrive: the confirmation email in your own inbox, the bank statement, or your customer account with the supplier. Never rely only on what the agent reports itself. One small trial task is safer than handing your whole mailbox to an agent.
How it works under the hood
According to Jones, the systems now being built for agents each answer a different question. Cloudflare's signed agents are about identity: who is sending the request. Google's AP2 is about mandate: has the user given the agent permission for this action. Stripe payment tokens and the Visa pilot are about payment credentials with limited scope. For your architecture, this means you put guardrails at tool level: limited browser rights, amount limits per transaction, a human-in-the-loop step for payments and logging of every action. Watch the prompt injection side: a web page can contain text that tells the agent to pay. When private data, untrusted web content and an outgoing payment channel come together, you have the lethal trifecta from chapter 21.
This news touches chapters 7 and 21 of the course AI(l) or nothing by Newway. If you follow the course, this subject returns there at a calmer pace.
What you can do with this
Want to know what this means for your business? Plan an introduction: half an hour, no sales pitch, but an honest answer to the question where to begin. Rather read on first? The course AI(l) or nothing is free and starts with the basics.
Written in response to a publication by Nate's Newsletter (Substack): https://natesnewsletter.substack.com/p/ai-agents-website-access
