The Agent-Ready Website Checklist

A website is agent-ready when an agent given only its domain can: discover its capabilities from a machine-readable document, identify the organisation and its accountable human, learn how to authenticate and pay, take one safe action, and receive a verifiable receipt — with no human navigation. The checklist is concrete: a well-known discovery document, capabilities as verbs, machine-readable pricing, a stated auth method, callable endpoints, and proof.

Test
Can an agent act from the domain alone?
Discovery
A well-known machine-readable document
Capabilities
Verbs, with machine-readable pricing
Proof
A verifiable receipt for actions

The checklist

Serve a discovery document at a well-known path; name capabilities as verbs; publish prices in exact units; state an authentication method; expose callable endpoints beside the human forms; name an accountable human; and, where the site transacts, provide a way to pay and a receipt to prove it. Each item is additive — the human site stays — and each maps to a primitive some estate property owns.

Related standards

agents.txtA2A Agent Card

Questions

How do I test my site quickly?

Give an agent only your domain and see if it can discover your capabilities, authenticate, pay, act once, and receive a verifiable receipt. Each step it cannot complete is a checklist item.

Do I need to rebuild my site?

No. Agent-readiness is additive: a machine-readable door and callable endpoints beside the existing human pages.

Keep reading

related
What Is an Agent-Native Website?
related
GEO vs SEO: Optimizing for Answer Engines
related
What Is /.well-known/agent?
related
agents.txt vs llms.txt
related
Agent Time to Action (ATTA)
referenced by
What Is Answer Engine Optimization (AEO)?
Discoverability & GEO
What Is llms.txt?
Discoverability & GEO
Structured Data for AI and Agents

By Michael Gord · published 2026-09-29 · part of the Agentic Encyclopedia. Dates are the day of publication; events are cited at their own dates.