Two agent protocols ship as major sites keep the doors shut
Two agent access protocols landed inside a day, both answering the same question: a customer's agent arrives at your site and nobody has decided whether to let it in. Sierra and Meta published the Personal Agent Protocol, Decagon open sourced PACT, and Amazon is reportedly turning agents away while Walmart does it by accident. Google also put fake author profiles on its deception list and opened UCP checkout onboarding to US merchants.
This Week's Signals
Sierra and Meta publish the Personal Agent Protocol with Walmart, Shopify and Stripe
Why it matters for your score
The spec expects you to declare how an agent reaches you, by website, API or your own agent, so if you have declared nothing the agent guesses and you lose the customer standing behind it.
Decagon open sources PACT, which splits an agent's identity from its authority to act
Why it matters for your score
Scoped permissions like orders:read and orders:cancel are becoming the unit of agent access, so you need to decide now which actions a stranger's agent may take on a logged-in account.
Amazon blocks Meta's agent while Yelp, eBay and Zillow reportedly do the same
Why it matters for your score
Walmart blocks agents by accident through human verification checks even while partnering with one, which is the more likely story at your site too.
Google calls AI headshots and invented credentials a form of deception
Why it matters for your score
Fabricated bylines now sit in the same documentation as cloaking, so if your content scaled on invented experts that is a ranking liability and a citation liability at once.
Google opens the UCP integration hub in Merchant Center to US merchants
Why it matters for your score
Checkout eligibility is now a product data attribute, which means your feed decides whether an agent in Search or Gemini can buy from you at all.
Emerging Audit Signals
Agent access is splitting into two separate problems: proving which agent is calling, and proving what that agent is allowed to do.
Two protocols landed in 24 hours, one for each half.
The specs are being written by the demand side.
Meta, Walmart, Stripe and Shopify want their agents let in, and your business gets handed a standard rather than consulted on one.
Almost nobody decides to block agents.
They block them by accident, with bot rules and human verification checks written for scrapers years before buyers started arriving with agents.
Google keeps putting agent readiness inside tools you already log into.
Agent checkout gets configured in Merchant Center, not in a new console you have to discover.
Authenticity is turning into a technical check.
Who wrote a page, and whether that person exists, is now documented quality criteria rather than a matter of taste.
What to do this week
- 1
Pull your bot management and WAF rules, then request your own pricing, product and booking pages as a logged-out agent would. A challenge page means you are unreachable, not protected.
- 2
Write down the permission scopes you would grant a customer's agent, such as read orders, cancel orders, update address. Both new protocols expect you to define these before you can adopt either.
- 3
If you sell in the US, check whether your Merchant Center product data carries checkout eligibility, and submit the UCP integration interest form while early access is open.
- 4
Check every byline on your site resolves to a real person with verifiable credentials. Then run /tools/ai-readiness-scan to see which pages agents can actually read and act on.
Sources
- ↗ Introducing Personal Agent Protocol, Sierra
- ↗ Introducing the Personal Agent Consent & Trust Protocol (PACT), Decagon
- ↗ The next hurdle for AI agents: getting websites to let them in
- ↗ Creating helpful, reliable, people-first content, Google Search Central
- ↗ About Universal Commerce Protocol (UCP) integration hub in Merchant Center