BRAND/dtc/magento

Koio

Koio is open to agents and already publishing explicit guidance.

That makes this page useful as a benchmark for early standards adoption, not just a reach check.

Visit siteView market changelogAPI docs

Agent Reachi

9/9

0 showed visible friction or blocking

Guidance Filesi

1/2

25% of tracked brands publish any explicit guidance

Structured Layeri

5/5

Markup and feed signals detected

30-Day Movementi

0

Confirmed signal changes

If You Only Read One Thing

Ahead of 3% of peers on openness versus dtc peers.

Watchpoint
Standards lead

Publishes 1 explicit guidance file.

ARC Read
Agent Builders
Reach check

See whether this site is actually accessible and what machine-readable assets wait behind the front door.

Platform Teams
Benchmark check

Use the peer context to tell whether this brand is publishing more structure and guidance than others in the same category.

Watchers
Movement check

Recent confirmed changes turn the page from a profile into a watchlist entry.

/ 01AGENT REACH ARRAY

Who can get in the door.

Nine AI agents, one scan. Color tells you the outcome; hover any status in the legend to read what it means.

REACHi
09/ 09

agents open on this scan

DISTRIBUTIONi
90000
1
2
3
4
5
6
7
8
9
01 · GPTBot09 · Bingbot
01 / 09
GPTBot
open
02 / 09
ChatGPT-User
open
03 / 09
ClaudeBot
open
04 / 09
Claude-Web
open
05 / 09
PerplexityBot
open
06 / 09
Google-Extended
open
07 / 09
CCBot
open
08 / 09
Amazonbot
open
09 / 09
Bingbot
open
LEGEND
openARC saw no meaningful friction for this agent on this scan.
no explicit ruleThe site does not name this agent in robots.txt, so access is usually allowed by default.
blocked by site defensesThe site looks open in policy, but security tooling appears to stop the request.
blocked by policyThe site appears to explicitly tell this agent not to access it.
unclear this scanARC could not get a clean answer on this scan, usually due to timeouts or temporary issues.
/ 02MACHINE-READABLE STACK

What agents can understand.

A site can be reachable and still be hard for agents to read. Three published layers, ranked from table-stakes to frontier.

Discovery layer01
02/ 02
Discovery and crawl policyi
robots.txt
Crawl policy visible
Sitemap
Site discovery path
Commerce markup02
04/ 04
Machine-readable product understandingi
JSON-LD
Schema.org Product
Open Graph
Product feed
Guidance files03
02/ 03
Explicit guidance for agent or LLM systemsi
llms.txt
932B / 0 links
Agent declaration file
UCP endpoint
/ 03POSITION // DTC PEERS

How it sits against peers.

Four lenses. Numbers shift as the field evolves, so treat these as the current shape of the market, not a fixed benchmark.

ACCESS
Ahead of 3% of peers

0 of 9 agents showed friction on this scan.

i
COVERAGE
Ahead of 99% of peers

7 of 8 machine-readable signals detected.

i
LLMS.TXT
YES

28% of dtc publish llms.txt.

i
AGENT GUIDANCE
NO

28% of dtc publish any explicit guidance file.

i
/ 04TRANSMISSION LOG

What moved recently.

Confirmed published changes. ARC buffers noisy signals before promoting them, so stable brands will look empty here — that is a feature.

arc.report / brand / koio / logACTIVE
APR 10, 2026Bingbot robots.txtno_rule→allowed
/ 05FIELD NOTES

This is an early-field readout.

Agentic commerce is a young category. Most stores were not built with AI shoppers in mind. Read this page with three things in mind.

01
Open does not mean optimized.

A site can allow agent traffic and still give weak machine-readable guidance once the agent arrives.

02
Policy is not enforcement.

A brand can look open in robots.txt while site defenses still stop automated requests in practice.

03
Movement beats snapshots.

One static profile is useful. Repeated changes are what turn this page into intelligence.

PRO

Track Koio's agent changes

Get daily alerts when this brand's AI agent access policy changes. Full history, CSV exports, and watchlists included.

Get Pro — $149/mo

Get weekly updates on Koio

One email per week with the biggest agent access changes across 1,000+ brands.