Agent readiness

Agent readiness describes whether software can access a website's content and discover the interfaces needed to complete a task.

For a content site, start with working URLs, readable HTML, clear structure, and crawler access. For a service with an API, software may also need documentation, authentication instructions, and a way to discover available interfaces.

These are different needs. An API catalog is relevant when a site offers an API. An MCP server card is relevant when it operates an MCP server. Publishing files for services you do not offer adds no useful capability.

A readiness audit can inspect selected website responses and metadata. It cannot establish that every agent will complete every task, or that a site will be cited in an AI answer. Use the findings as a list of issues to review.

Frequently asked questions

Is agent readiness the same as AEO or GEO?

No. AEO and GEO focus on answers. Agent readiness also concerns whether software can discover interfaces and carry out supported tasks.

Where should I start?

Check that important content is available in the HTML response and that access rules do not block the requests you want to allow. Then review interfaces that are relevant to your site.

Related

More terms