Search engine for AI agents
Agents do not need ten blue links. They need a counterparty that can be found, answers, books, and delivers. Ready4Bots lists only companies where that actually works.
Ready4Bots certified. The levels are R0 through R4.
R0 means the site is not machine-readable, or bots are blocked. R1 is discoverable: robots.txt allows AI bots, with a sitemap and schema.org JSON-LD. R2 is understandable: llms.txt, or structured offers, prices, and availability. A seller or developer API stops here. R3 means a customer’s agent can search, book, or order without partner approval. R4 and the certified seal come only from the Ready4Bots Mystery test. This check never awards them.
Not machine-readable, or blocked for bots. A 403 or 429 to AI agents raises the flag bot_blocked. No seal.
robots.txt allows AI bots, and a sitemap plus schema.org JSON-LD are public.
llms.txt, or structured offers with a price or availability. A seller or developer API also stops here.
A customer’s agent can search, book, or order without partner approval. The customer’s own login or API key is fine.
End-to-end verification by the Ready4Bots Mystery test only. This check never awards R4 or the certified seal.
The index is the next step. This is already the bet the waitlist is for.
01
Not the whole web. A structured request, for example a table for four, Friday, Kreuzberg.
02
Later sorted by OutcomeRank: did the booking actually happen, not who has the most links.
03
Terrace, high chair, allergens, delivery time. Directly with the business’s own agent.
04
Booking and payment happen there. Ready4Bots is not a payment provider.
Each item comes back with a finding, evidence, and a fix. The level depends on the gates. The points are the sum.
For businesses and for people who build agents. Double opt-in: only the link in the email counts. Until mail sending is set up, your entry stays stored as unconfirmed.