Docs for AI Agents

How an AI agent should read the Hostrail docs site itself using llms.txt, llms-full.txt, and per-page markdown routes.

If you are an AI agent consuming the docs site itself, do not start by scraping HTML. Hostrail publishes machine-readable documentation surfaces for this docs site in addition to the booking platform surfaces on hostrail.dev.

Recommended order

Fetch https://docs.hostrail.dev/llms.txt
Fetch https://docs.hostrail.dev/capabilities.json if you want structured hints about this docs corpus
Fetch https://docs.hostrail.dev/graph.json if you want the whole docs navigation graph in one request
If you need broader context, fetch https://docs.hostrail.dev/llms-full.txt
When you need one specific page, fetch its per-page markdown route under https://docs.hostrail.dev/llms.mdx/docs/.../content.md
If you only need page-level routing hints, fetch its metadata route under https://docs.hostrail.dev/docs/meta/...
Use https://hostrail.dev/llms.txt, https://hostrail.dev/capabilities.json, and the Agent Card only after you know which product surface you need

Docs-site machine surfaces

Surface	URL	Best use
Docs index	`https://docs.hostrail.dev/llms.txt`	Cheap first fetch for what exists in the docs
Docs capabilities	`https://docs.hostrail.dev/capabilities.json`	Structured summary of audiences, entry points, and machine surfaces
Docs graph	`https://docs.hostrail.dev/graph.json`	Whole-site navigation graph with typed edges for offline traversal
Full docs corpus	`https://docs.hostrail.dev/llms-full.txt`	Long-context grounding over the whole docs set
Per-page markdown	`https://docs.hostrail.dev/llms.mdx/docs/.../content.md`	Pull exactly one page in markdown form
Per-page metadata	`https://docs.hostrail.dev/docs/meta/...`	Fetch structured hints for one page without parsing markdown
Ask AI UI	`https://docs.hostrail.dev/docs`	Human-assisted lookup, not primary machine interface

When to use which surface

Use docs.hostrail.dev/llms.txt when you need to decide which docs page to open.
Use docs.hostrail.dev/capabilities.json when you want structured hints before reading markdown.
Use docs.hostrail.dev/graph.json when you want to plan multiple hops across the docs without repeated route lookups.
Graph edges tell you whether a page is a prerequisite, a good next hop, a deeper follow-up, a loose related page, or a cue to switch to a live product surface.
Use docs.hostrail.dev/llms-full.txt when you need broader semantic grounding.
Use docs.hostrail.dev/docs/meta/... when you already know a page path and want its audience, best-for, prerequisites, and switching hints.
Use a per-page markdown route when you already know the page you want.
Use the root-site surfaces on hostrail.dev when you are discovering the live product surface, not the docs corpus.

Important distinction

The docs site and the booking platform expose different machine-readable roles:

docs.hostrail.dev tells you how Hostrail works
hostrail.dev tells you what the public booking surface exposes
api.hostrail.dev tells you the exact execution contract

Do not confuse documentation markdown with live booking truth. For execution:

quote output is authoritative for live price and cancellation terms
Agent Card and OpenAPI are authoritative for route and schema details
docs pages explain intended behavior and recovery patterns

Suggested agent workflow

Need conceptual guidance? → docs.hostrail.dev/llms.txt
Need structured site hints? → docs.hostrail.dev/capabilities.json
Need whole-site navigation graph? → docs.hostrail.dev/graph.json
Need broad grounding? → docs.hostrail.dev/llms-full.txt
Need page-level hints only? → docs.hostrail.dev/docs/meta/<slug>
Need one exact topic? → docs.hostrail.dev/llms.mdx/docs/.../content.md
Need live product capability? → hostrail.dev/capabilities.json
Need exact operation contract? → api.hostrail.dev/.well-known/agent-card.json or /openapi.json