DocsDocsAgents

Agent files manifest

Browse Enad agent files, route guides, and version tracks before handing work to an agent.

Agent setup

Files agents can load

Use these files when an agent needs the right Enad docs route, supported surface version, or compact starting point.

Open JSON
Start small
/llms.txt
Need breadth
/llms-full.txt
Need structure
/ai/manifest.json
Updated
Apr 25, 2026

Files to load

LLMs Index/llms.txtLLMs Full/llms-full.txtManifest/ai/manifest.json

How to choose

Open the smallest file that can route the task.Updated Jul 1, 2026
Verify exact SDK, API, Search, and event facts in the matching reference.Use the larger bundle only when the task crosses several Enad areas.

Route guides

Agent guidesGuideAgent quickstartQuickstartAPI route guideAPI GuideAgent filesAgent File GuideEnad app auth.mdIntegration GuideAgent files manifestManifest BrowserMCP serverMCP GuidePrompt recipesPrompt RecipesReact SDK agent guidePackage GuideReact SDK agent commerce and Search handoffPackage GuideReact SDK discovery and importsPackage GuideReact SDK agent theme and iconsPackage GuideTypeScript SDK agent guidePackage Guide

Versions and surfaces

React SDKPackage · CurrentTypeScript SDKPackage · CurrentManagement APICurrentShopper APICurrentAuth APICurrentAsset library reads and DAM administrationAPI · CurrentIntegrations APICurrentDAM / Media APICurrentSearch GraphQLCurrentEventsEvent Catalog · Current

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. Use /llms-full.txt when the task spans several Enad areas. Use /ai/manifest.json when the agent needs structured route data.

Agents should use this human route for inspection and /ai/manifest.json for structured ingestion.

Agent files manifest

# Agent files manifest 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. Use /llms-full.txt when the task spans several Enad areas. Use /ai/manifest.json when the agent needs structured route data. Agents should use this human route for inspection and /ai/manifest.json for structured ingestion.