This week on Now Shipping, Mike Belsito explores why personal agents are getting stuck across the web, and what those failures reveal about the products we build. From Walmart’s checkout checks to Yelp’s paid access model, businesses are taking very different approaches to agent traffic. Sometimes, the decision comes down to a security setting nobody on the product team has reviewed.
Mike also examines Wikimedia’s concerns about suspected OpenAI agent activity and the proposed Personal Agent Protocol from Meta and Sierra. What could agent authentication solve, and what still needs to be fixed inside your product?
For product teams, the starting point is practical: test a critical flow with an agent, find out where it fails, and decide what it should be allowed to do.
In this episode
- Why welcoming agents publicly doesn’t guarantee they can use your product
- How CAPTCHAs, bot filters and infrastructure defaults shape your agent policy
- What Wikimedia’s findings raise about agent permissions and responsibility
- What the proposed Personal Agent Protocol aims to address
- How agent traffic could affect pricing, costs and product analytics
Chapters
00:00 MTP Chicago and this week’s briefing
01:00 Why agents are failing at Walmart’s checkout
02:00 Cloudflare defaults and the hidden agent policy
03:00 How Yelp, Delta, eBay and Zillow handle agents
04:00 Balancing customer access with security
05:00 Wikimedia’s findings on suspected OpenAI agents
06:00 Introducing the proposed Personal Agent Protocol
07:00 What a protocol could solve, and its limitations
08:00 Test your product’s real agent policy
09:00 Design the failure state and check your settings
10:00 Review what agents can change
11:00 Agent access, pricing and infrastructure costs
12:00 Measuring agent activity and rising customer expectations
13:00 Three questions every product team should answer
Key takeaways
- Your product already has an agent policy. Bot settings, human checks, terms of use and vendor defaults collectively determine how it treats agents.
- Test a flow that matters. Ask an agent to complete a sign-up, checkout or booking, then record every point where it gets stuck.
- Design the handover. If an agent cannot continue, give the customer a clear explanation and a way to finish without losing their progress.
- Make permissions deliberate. Review what agents can read and change, and where explicit approval is needed.
- Check your measurement. Understand whether your analytics distinguish agent activity from human activity before making access or pricing decisions.
If an agent arrived at your product tomorrow, could you identify it, understand who sent it and explain what it was allowed to do?
