Begin with the basics, then dig into bot access, product data, security, and the standards shaping AI shopping.
The plain-English introduction to AI agents as shoppers, and what retailers need to prepare.
Retail RealityWhy brand storytelling disappears when an agent can only parse fragments of the page.
SecurityThe infrastructure built to protect retailers is now blocking legitimate AI agents.
AI agents are becoming shoppers. Learn what that means for your business and how to prepare.
Emerging standards like UCP, MCP, and WebMCP that will define the next era of e-commerce.
From Archie to GPTBot, the web keeps fighting the same access problem.
WAFs cannot reliably tell a human-backed agent from hostile automation.
What happens when pages expose callable tools inside the user's browser session.
345+ European retail sites scanned. The agent sees what it can parse, not your brand story.
Why missing GTINs and weak product identity break agent matching.
Why feeds, product pages, firewalls, and retailer listings all shape whether agents can buy.
Google AI Max reads Merchant Center attributes like a document. Agents use the same logic.
Site averages hide the exact products that will fail agent discovery or checkout.
An open extension for declaring per-product agent purchase terms.
ACP, UCP, MCP, TAP, VIC, and MAP: what each protocol does and what they still need from you.
Every brand listed on checkout.directory as UCP-ready still scored Not Ready for agentic commerce.
How emerging protocols will shape agent identity, payment, and checkout.
Updated for Poppy 1.0: what discovery, UCP and merchant controls establish, and what still needs testing.
Claude for Commerce makes the agent layer cheaper to build. It does not make a retailer's catalogue, cart, or checkout agent-ready.
Why the consortium's market problems map directly to what we see in readiness scans.
Bot protection is still necessary. The problem is that AI shopping agents are automated traffic too, and many sites now reject agents acting on behalf of real customers.
Provider breakdown · 119 sites
How hard is agent allowlisting?
Data from 486 unique e-commerce sites scanned by Aidō Lighthouse as of May 2026. Bypass difficulty reflects the merchant effort required to allowlist verified AI agent user agents, not malicious circumvention. Learn how protocols like Visa TAP and ACP are creating verifiable agent identity →
The scanner reads third-party websites on your behalf. Those sites can contain anything. Our job is to analyze them accurately without letting what they contain touch anything it should not. That shapes every security decision we make. Reused verbatim from our full Scanner Policy page below.
Most SaaS platforms worry about what users submit. We also worry about what scanned URLs submit back. A merchant site could return a page with prompt injection payloads designed to manipulate our AI analysis, or HTML crafted to trigger SSRF against our internal infrastructure. These are not theoretical.
We treat every scanned URL as potentially hostile. Prompt injection defense applies to all AI-processed content. SSRF checks run before any outbound request. Security events are logged in enough detail to tell a legitimate scan from an attempted exploit.
We aim for OWASP ASVS Level 2 compliance. The controls below are implemented and active, not aspirational.
The scanner signs every outbound request. The public key and scanner policy are at /.well-known/agent-identity.json. Any site operator can verify a request came from us rather than something claiming to be us. Signing keys rotate via GCP Secret Manager. Every request carries a signed, stable identity.
To block the scanner, add this to your robots.txt. The scanner respects it without exception.
To remove your site from the scan queue entirely, email info@aido-labs.co. The scanner runs on Google Cloud Run in us-central1 (Iowa); egress IPs come from Google's published Cloud ranges at gstatic.com/ipranges/cloud.json, filtered to scope: us-central1.
Page HTML, HTTP response headers, and structured data (JSON-LD, schema.org markup); protocol endpoint responses (robots.txt, llms.txt, /.well-known/* endpoints, openapi.json); payment method signals detected from public page content; bot detection signals encountered during the scan (WAF provider, challenge type). No credentials, session data, or personal information is collected. Scan results are kept for 90 days and visible only to the account holder who ran the scan.
If you find a security issue, email info@aido-labs.co. We aim to respond within 48 hours. No bug bounty program yet, but we will acknowledge responsible disclosure publicly on request.