Agent files manifest
Browse Enad agent files, route guides, and version tracks before handing work to an agent.
Files agents can load
Use these files when an agent needs the right Enad docs route, supported surface version, or compact starting point.
- Start small
- /llms.txt
- Need breadth
- /docs.zip
- Full text
- /llms-full.txt
- Need structure
- /ai/manifest.json
- Updated
- Apr 25, 2026
Files to load
How to choose
Route guides
Versions and surfaces
Start here when you want to inspect the files and route guides an agent can load before handing off Enad work. The panel above links to the public agent files and shows which route guides are available.
Use it when an agent or maintainer needs to answer:
- Which agent route is the narrowest safe starting point?
- Which agent file should a client request first?
- Which version track applies to package, API, Search, Media, Events, or integration work?
- Which Enad area should the agent open next?
Agent usage
For most agent tasks, start with /llms.txt. Reach for /docs.zip when a tool needs local markdown files. Use /llms-full.txt when the task spans several Enad areas. Load /ai/manifest.json when the agent needs structured route data.
Agents should use this human route for inspection, /ai/manifest.json for structured ingestion, and /.well-known/agent-skills/index.json for skill discovery.