What Is an Agent-Native Website?

An agent-native website is one an autonomous agent can use, not just read. It serves a machine-readable document declaring its capabilities as verbs, keeps a stable identity and an accountable human, publishes prices and policies a machine can parse, and exposes its actions through callable endpoints rather than forms built for people. Becoming agent-native means adding a machine front door beside the human one — not replacing the site, but making it legible to software.

Test

Can an agent act, not just read?

Needs

A machine-readable door + callable endpoints

Prices

Machine-readable, exact units

Keeps

A stable identity and accountable human

A machine front door

Adding an agent-native surface is additive: the human site stays, and a machine-readable door is published beside it so an agent can discover capabilities, understand authentication and payment, and call an action. The site becomes something an agent can transact with rather than a page it has to interpret.

The readiness checklist is concrete: a discovery document at a well-known path, capabilities named as verbs, machine-readable pricing, a stated authentication method, an accountable human, and — where the site transacts — a way to pay and a receipt to prove it. Each of those is a page in this encyclopedia and a primitive some property owns.

Related standards

agents.txtA2A Agent CardMCP

Questions

Do I have to rebuild my website to be agent-native?

No. It is additive: you publish a machine-readable door and callable endpoints beside the existing human site.

How do I test whether my site is agent-ready?

Check that an agent, given only your domain, can discover your capabilities, learn how to authenticate and pay, take one action, and receive a verifiable receipt.