Agent files
How to choose between /llms.txt, /llms-full.txt, /docs.zip, skills discovery, and /ai/manifest.json before giving an agent Enad docs.
Start here when a person, tool, or agent needs to choose the right Enad file before opening SDK, API, Search, Media, Events, or integration docs.
Choose the file
Use /llms.txt for short route selection and the smallest safe starting points. Do not use it for full SDK or API detail.
Use /llms-full.txt when the task spans multiple Enad areas. Do not use it as exact package, endpoint, or GraphQL field truth.
Use /docs.zip when a tool needs the generated agent files and public AI guidance pages as a local markdown archive for grep, embeddings, or offline ingestion.
Use /ai/manifest.json for structured route data, version tracks, and copy guidance. Do not treat it as a replacement for package docs, OpenAPI, Search reference, or event catalog.
Use /.well-known/agent-skills/index.json when an agent runtime can install a docs skill through discovery. Legacy clients can read /.well-known/skills/index.json.
Start with the smallest file that answers the routing question. Move to the larger bundle only when the task spans multiple domains.
What agents can rely on
The public agent files are routing aids. They include:
- stable docs routes that help agents choose the right surface.
- version-track data for supported packages and APIs.
- reference hints for SDK packages, APIs, OpenAPI specs, and Search.
- copy guidance for quoting, summarizing, and verifying before coding.
- a downloadable archive and discoverable docs skill for tools that work best from local context.
What agents must still verify
These files do not replace the references that own exact behavior. Before writing code, verify package exports, component props, and hook signatures in package reference.
For API or Search work, verify endpoint fields, GraphQL fragments, and event payloads in the owning reference. Playground-only runtime behavior stays in the playground.
Contract scope
Use agent files to choose the route. Use the matching reference to verify exact facts.
| Question | Trust this source |
|---|---|
| Which docs route should an agent open first? | /llms.txt, /llms-full.txt, /docs.zip, or /ai/manifest.json |
Which React or TypeScript package track does latest describe? | /ai/manifest.json and the version-track page |
| What is the exact SDK export, prop, hook, helper signature, or runtime behavior? | SDK package reference |
| What is the exact REST path, request field, response field, or auth rule? | API reference and OpenAPI inputs |
| What is the exact Search operation, variable, fragment, or generated type? | Search reference and package reference |
| What belongs to the live runtime sandbox? | the playground and https://sdk.enad.io/sandbox |
Practical selection rule
- Use /llms.txt to pick the smallest relevant docs route.
- Use /ai/manifest.json when a tool needs route data or version-track context.
- Use /docs.zip when a tool needs local markdown files.
- Use /llms-full.txt only when the task crosses multiple Enad domains.
- Before writing exact code, jump from the chosen docs route to the owning package, OpenAPI, or Search reference.