Actum
Sign inScan free →
● Live audit

The Flagship 8.

The eight brands the platforms put front-and-centre for agent checkout. We check what an AI agent actually finds on their own domain — not the catalogue feed the platform hosts. This page is checked live; it's exactly what our agent sees.

0 of 8expose a machine-readable agent.json on their own domain
3 of 8have no agent-facing file at all — no llms.txt, nothing
4 of 8publish an llms.txt — and that's as far as it goes
MerchantProgram/llms.txt/agent.json/.well-known/agent.json
GlossierChatGPT · ACP✓✕✕
VuoriChatGPT · ACP✓✕✕
SpanxChatGPT · ACP✓✕✕
SKIMSChatGPT · ACP✕✕✕
TargetGoogle✓✕✕
WalmartGoogle✕✕✕
EtsyGoogle✕✕✕
WayfairGoogle—✕✕
✓ found · ✕ not found · — couldn't reach (blocked or timed out). Checked 7 Aug 2026, 01:19 UTC · re-audited automatically. The canonical /.well-known/agent.json path follows the agent.json proposal.

Being in the feed isn't the same as being ready.

These are the best-resourced, earliest-integrated sellers in agent commerce — and most of them have a bare front door. The platform built the rail and hands over their catalogue, but when an agent lands directly on the brand's own domain, there's often nothing for it to read. If the gap is this wide for the launch partners, it's wider for everyone else.

A platform connection makes you reachable. It doesn't make you readable on your own domain — and that's still on you.

Note the honest nuance: this isn't “they do nothing.” Some publish an llms.txt. But none expose the actionable agent.json an agent needs to know what it can do — browse, price, buy, contact — which is the difference between being described and being transactable.

We checked them live. We'll check yours too.

Free, in about 30 seconds — see exactly where an agent drops out on your site.

Scan your site free →Book a demo