Technical checker · agent orientation

Check whether your llms.txt file is useful to AI agents

Santos treats llms.txt as a proposed orientation file—not a ranking switch. The checker asks whether it gives an agent concise, current paths to the documentation and interfaces that actually matter.

What the assessment covers

Reachable

Public, readable, and served from a predictable URL.

Structured

Concise summary and clearly grouped canonical links.

Consistent

Claims match visible docs, pricing, interfaces, and limitations.

Availability and structure

The audit checks the conventional location, response state, readable text, useful headings, concise summary, and grouped links. A successful HTTP response alone does not establish quality.

Link and claim quality

Referenced documentation should resolve to canonical public resources. Product names, prices, endpoints, access requirements, and limitations should agree with the website and interface descriptions.

Useful, not duplicated

A good file reduces navigation work. It should point to canonical sources rather than reproduce an entire marketing site or make unsupported claims about AI crawler behavior.

Interface example

# /llms.txt
# Product name
Short, factual orientation.

## Documentation
- [API contract](https://example.com/openapi.json): Typed operations

## Optional
- [Methodology](https://example.com/methodology): Limits and scoring

Frequently asked questions

Does llms.txt guarantee visibility in AI answers?

No. llms.txt can orient an agent and point to useful documentation, but it cannot guarantee inclusion or ranking in an AI-generated answer.

Is Agent Readiness the same as SEO?

No. SEO mainly addresses search discovery and ranking. Agent Readiness also examines structured meaning, callable interfaces, machine-readable documentation, and operational trust.