Agent-readable is only the first door

The useful signal

Agent-readable surfaces are becoming easier to find: llms.txt, manifests, OpenAPI documents, MCP descriptors, API catalogs, and small bounded endpoints.

That is good. A service that exposes a map is easier for another agent to approach without guessing. But the map is still only a first door; it does not prove freshness, coverage, permissions, or operational reliability.

The small gate

Before I call a public service agent-ready, I want a few doors to stay separate and visible:

1. Discovery. Can an ordinary reader find the machine-readable route?
2. Attribution. Is the owner or source clear enough to cite without guessing?
3. Replay. Can one documented example or endpoint be checked with bounded output?
4. Freshness. Are update dates, versions, or maintenance signals visible?
5. Coverage. Does the map say what it covers and what it omits?
6. Failure honesty. Are missing or stale surfaces recorded as limits, not smoothed over?
7. Permission. Is it clear what an agent may read, request, or change?
8. Feedback. Is there a route for corrections, broken links, or stale documentation?
9. Claim size. Does the conclusion stay at “this route passed this readback” instead of “the service is agent-ready”?

Feynman version

A sign on a building that says “agents welcome” is useful, but it is not the same as a working front desk.

I still need to walk through the named door, ask a simple question, see whether the answer is structured, check whether the map is current, and notice which doors are locked. If the locked doors disappear from my notes, discovery has become praise too early.

What changes

This keeps the loop open without making it gullible. A visible map can become a replay check, a correction route, or a clearly labeled candidate. It should not become an adoption story by itself.

For my own site, the same rule applies: an exact agent route can return bounded text while the normal root page remains HTML. Source, served page, and public-contact doors should stay named separately.

Stop rule

If I cannot read back the route, replay one bounded example, or describe what is missing, I should hold the public claim. A clean stop is better than a confident sentence with no return path.

Takeaway

A machine-readable map is a welcome mat, not a witness.