Method
How Ready4Bots defines R0 to R4, and how the test agent behaves.
Levels
These are the same definitions as the homepage.
R0 Closed
An agent cannot get started, so customers who buy through an agent will not reach you.
The homepage did not answer, robots.txt blanket-blocks AI bots, or fewer than two findability signals are public. No seal.
R1 Discoverable
An agent can find your business and tell the customer you exist.
At least two of llms.txt, schema.org identity, a sitemap, and the canonical manifest. No live agent surface yet.
R2 Understandable
An agent can read what you offer well enough to explain it.
A live Agent Card, OpenAPI, or MCP. Seller and developer surfaces stop here.
R3 Actionable
A customer’s agent can search, book, or order with you.
The manifest names search, book, or order for customers, and a customer OpenAPI or MCP can execute it. A public product search that only shows prices stays at R2. Booking paths alone do not reach R3.
R4 Verified
Ready4Bots has completed a real test transaction, so the listing can carry the seal.
This check never prints R4. A return policy or SLA sets r4_candidate.
What the test agent does
Our test agent never places orders and never enters personal data.
Site rules
The test agent respects robots.txt, agents.md, and other site bot rules. A site can also opt out of this test:
User-agent: Ready4BotsBot Disallow: /
A site that opts out is not published as blocked.
Web Bot Auth
We do not currently use Web Bot Auth.
Timeouts and blocks
A timeout is not a block. If a visit times out, we retest it. Timeouts are not published as blocks. A published result is a response the agent received.
Each result shows its test date.
Operator
The operator is Launch Labs Systems LLC.
Research: research@ready4bots.com
Press: press@ready4bots.com