What agent-ready actually means: the five levels

Every few years the industry adopts a phrase faster than it agrees on a meaning. Mobile-first went that way. Omnichannel went that way. Agent-ready is going that way right now, and by the end of the year every vendor in the space will have it on a slide.

So here is a definition specific enough to argue with. Agent-readiness is not binary. It is a ladder with five rungs, and each rung answers a different question about what an AI can do with your store.

Level 1: Invisible

At Level 1 a machine requesting your pages gets a shell. The product grid assembles in the browser, the specs live inside images, the offers are a PDF, and there is little or no structured data describing any individual product. Often the crawler policy blocks AI agents by default and nobody in the store knows.

The important thing about Level 1 is that it is completely compatible with a great website. Fast, attractive, converting well, redesigned last year. Human experience and machine legibility are separate axes, and almost nobody was building for the second one until recently. This is where most businesses start when they first run the check, typically somewhere around 21 out of 100.

Level 2: Readable

At Level 2 a machine can establish the basics. There is valid schema.org markup identifying the business as a LocalBusiness of the right type, with a real address, hours and phone number. Some product data is present in a parseable form. The sitemap is clean and the robots policy does not accidentally exclude the agents you want.

An assistant at this level can confirm you exist and roughly what you are. It cannot reliably answer a question about a specific product, because the product data is partial, inconsistent, or stale. In practice a Level 2 store gets mentioned but not recommended, because the model has nothing concrete enough to stand behind.

Level 3: Understood

Level 3 is where structured data becomes complete rather than decorative. Everything you sell carries proper Product, Service and Offer markup: what it is, what it includes, what it excludes, how long it takes, what it costs, whether it is available, photos, and a link that resolves to the right page. Detail is decoded into text rather than trapped in a PDF or an image. Prices and promotions are structured objects with conditions and expiry dates rather than a marketing graphic.

Now an assistant can answer factual questions about your catalog: can you do this particular job under a certain price, what does that package actually include, how soon could it happen. This is a real threshold. It is the first level at which you can be the source of an answer instead of a footnote in someone else’s.

The limitation is freshness. Level 3 still depends on crawling, which means the assistant is working from a snapshot. If a unit sold this morning, the answer may be wrong this afternoon, and being confidently wrong about availability is its own kind of damage.

Level 4: Answerable

Level 4 replaces the snapshot with a connection. Instead of waiting to be crawled, your store exposes a live endpoint that assistants can query in the moment, in practice a Model Context Protocol server, a published ChatGPT app, or both.

The difference is not subtle. At Level 3 the assistant recites what it read. At Level 4 it asks your systems a question and reports what came back, right now. Search by need and budget, compare two units, check whether something is still on the shelf, quote the current program. The answer is as current as your feed, which is the standard a shopper already expects from every other category they buy in.

This is also the level at which you get a named presence rather than an incidental mention. A buyer can add your store inside the assistant and shop it directly. You are no longer hoping to be retrieved. You are connected.

Level 5: Agent-Native

At Level 5 the assistant stops describing and starts doing. It has tools, and the tools do the work your front desk does: price a real job from your real rates, check what is genuinely free rather than guessing, turn “sometime this week under 500” into an actual slot at an actual figure, answer a policy question the way you would answer it, and take the booking or drop a structured enquiry into your CRM without the customer ever leaving the conversation.

It also means being present on more than one surface, because buyers are not all in the same place. The same underlying model of your store answers over MCP, inside a ChatGPT app, to an agent operating your own website in the browser through WebMCP, and to the answer engines that read the open web.

This is the top of the checker’s scale, 100 out of 100, and it is where the live Parleon tenants sit today. Not as a projection, as a number anyone can reproduce by running the same public check against the same live sites.

Why the ladder matters more than the badge

Two things follow from framing this as levels rather than a yes or no.

The first is that you can locate yourself honestly. Most stores are not at zero. They have some markup, a decent sitemap, maybe a vendor who did a competent job on the basics. Knowing you are at Level 2 and not Level 4 tells you exactly which work remains, and it is usually less work than people fear.

The second is that claims become checkable. When someone tells you their product makes you AI-ready, the useful follow-up is which level, measured how, verifiable where. A number produced by a public checker against a live URL is a different kind of assertion than a bullet on a slide. That is the entire reason we made the checker public even though anyone, including our competitors, can run it.

Ladders are also honest about sequencing. You cannot skip to Level 5. Live tools built on top of catalog data that a machine cannot parse correctly will confidently produce wrong answers faster. The unglamorous work at Levels 2 and 3 is what makes the impressive work at Levels 4 and 5 trustworthy.

Start by finding out which rung you are on. Everything else is a decision about how far up you want to go.