Back to Home
Learning hub

A practical guide to agentic commerce.

Begin with the basics, then dig into bot access, product data, security, and the standards shaping AI shopping.

Aido agent readiness analysis dashboard
Agent readiness analysis What machines actually see

Article archive

The full library.

Grouped by theme for easier reading: security, standards, product data, and market research.

Start Here

Foundations

What is Agentic Commerce?

AI agents are becoming shoppers. Learn what that means for your business and how to prepare.

The Future of Shopping

Emerging standards like UCP, MCP, and WebMCP that will define the next era of e-commerce.

Thirty years of bots: the cat-and-mouse game that was never necessary

From Archie to GPTBot, the web keeps fighting the same access problem.

Security & WAFs

Access, controls, and risk

The WAF paradox: why protection infrastructure is blocking AI agents

WAFs cannot reliably tell a human-backed agent from hostile automation.

WebMCP: when your website starts handing agents the keys

What happens when pages expose callable tools inside the user's browser session.

What AI agents actually see when they visit your website

345+ European retail sites scanned. The agent sees what it can parse, not your brand story.

Product Data

Feeds, GTINs, and per-product readiness

Listed. In stock. The wrong bottle.

Why missing GTINs and weak product identity break agent matching.

Your product feed is your campaign now

Google AI Max reads Merchant Center attributes like a document. Agents use the same logic.

Per-product, not per-site: why every item needs its own agent score

Site averages hide the exact products that will fail agent discovery or checkout.

AOCF 1.0 — Agent-Optimised Catalogue Feed

An open extension for declaring per-product agent purchase terms.

Standards & Payments

Protocols and infrastructure

The agentic payments map

ACP, UCP, MCP, TAP, VIC, and MAP: what each protocol does and what they still need from you.

UCP Is Not Enough

Every brand listed on checkout.directory as UCP-ready still scored Not Ready for agentic commerce.

The Future of Shopping

How emerging protocols will shape agent identity, payment, and checkout.

Market Research

Reports and analysis

2026 AI Commerce Readiness Index

Data from 500+ retailer scans and the infrastructure gaps blocking autonomous commerce.

Your AI assistant is only as good as your infrastructure

Most retail brands have launched AI agents on systems never designed to support them.

Regional Analysis

Market-specific findings

Latin America's AI Commerce Gap

75 LATAM e-commerce sites scanned. Average transactability: 29.4/100.

El mercado de belleza en México y el muro del comercio agéntico

19 marcas líderes analizadas. Las marcas tienen el mejor contenido y el peor checkout.

News

Company and ecosystem updates

Aidō Lighthouse joins the Agentic Commerce Consortium

Why the consortium's market problems map directly to what we see in readiness scans.

Scan intelligence

Twenty years of keeping bots out. Now we need to let the right ones in.

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.

May 2026 dataset
486
e-commerce sites scanned and analysed
unique domains
25.7%
block or challenge AI agent access
125 of 486 sites
40%
of blocked sites use hCaptcha
48 of 119 identified
#1
identified blocker is hCaptcha
Cloudflare doubled month-on-month

Provider breakdown - 119 sites

hCaptcha
48
Cloudflare
26
Google reCAPTCHA
13
Generic WAF
13
DataDome
5

How hard is agent allowlisting?

Rate limitersTrivial
Cloudflare WAF rulesEasy
Imperva / AWS WAF / SucuriModerate
Akamai Bot ManagerHard
DataDome / PerimeterX / HUMANHard
Kasada / Shape / F5Very hard

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 →