# Enad docs agent files

Agent routes for Enad SDKs, APIs, Search, playground boundaries, and theming guidance.

Generated: 2026-04-25T12:40:51.965Z

## Agent files

- https://docsv3.enad.io/docs.zip: downloadable markdown archive for local grep and agent ingestion.
- https://docsv3.enad.io/llms-full.txt: complete agent guidance bundle.
- https://docsv3.enad.io/ai/manifest.json: structured route metadata for agents and tools.
- https://docsv3.enad.io/.well-known/agent-skills/index.json: Agent Skills discovery for tools that install docs skills.

## Core routes

- https://docsv3.enad.io/ai: Agent guides - Enad entry points for agent-guided implementation.
- https://docsv3.enad.io/ai/agent-quickstart: Agent quickstart - Give an agent the right Enad context for SDK, API, Search, and theming tasks.
- https://docsv3.enad.io/ai/apis/latest: API route guide - Agent routing for Enad REST APIs, Search GraphQL, Events, Media, and MCP workflows.
- https://docsv3.enad.io/ai/artifacts: 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.
- https://docsv3.enad.io/ai/enad-app-authmd: Enad app auth.md - Guide for Enad app auth.md discovery, email-claimed registration, OTP completion, and scoped API-key usage.
- https://docsv3.enad.io/ai/manifest: Agent files manifest - Browse Enad agent files, route guides, and version tracks before handing work to an agent.
- https://docsv3.enad.io/ai/mcp-server: MCP server - Connect to the hosted Enad MCP server, verify public docs tools, sign in for protected tools, and use preview/apply workflows safely.
- https://docsv3.enad.io/ai/prompts: Prompt recipes - Copy-paste-safe prompt recipes for Enad React SDK, TypeScript SDK, Search, APIs, Media, Events, and theming tasks.
- https://docsv3.enad.io/ai/react-sdk/latest: React SDK agent guide - Agent guidance for React SDK provider setup, component selection, Search runtime, storefront composition, and runtime theming.
- https://docsv3.enad.io/ai/react-sdk/latest/commerce-search-handoff: React SDK agent commerce and Search handoff - Help agents split shopper UI composition from Search GraphQL and purchase-side contract truth.
- https://docsv3.enad.io/ai/react-sdk/latest/discovery: React SDK discovery and imports - Route agents to the right React SDK family and public import surface without inventing exports or props.
- https://docsv3.enad.io/ai/react-sdk/latest/theme-and-icons: React SDK agent theme and icons - Guide agents through provider nesting, theme hashes, component sets, and icon/runtime boundaries.
- https://docsv3.enad.io/ai/ts-sdk/latest: TypeScript SDK agent guide - Agent guidance for using the Enad TypeScript SDK and Search package surface while preserving exact reference boundaries.

## Active version tracks

- React SDK latest: https://docsv3.enad.io/react-sdk/latest; status current; surface @enadhq/enad-react-sdk; reference https://docsv3.enad.io/react-sdk/latest; Exact React SDK imports, props, hooks, component parts, package versions, and runtime behavior require SDK package reference for this track.
- TypeScript SDK latest: https://docsv3.enad.io/ts-sdk/latest; status current; surface @enadhq/enad-ts-sdk; reference https://docsv3.enad.io/ts-sdk/latest; Exact TypeScript SDK exports, method signatures, generated types, package versions, and runtime behavior require SDK package reference for this track.
- Management API latest: https://docsv3.enad.io/apis/management/latest; status current; surface management-api; reference /swagger/management-api.json; Endpoint paths, methods, parameters, request bodies, responses, enums, and auth schemes must come from the Management API OpenAPI reference.
- Shopper API latest: https://docsv3.enad.io/apis/shopper/latest; status current; surface shopper-api; reference /swagger/shopper-api.json; Endpoint paths, methods, parameters, request bodies, responses, enums, and auth schemes must come from the Shopper API OpenAPI reference.
- Auth API latest: https://docsv3.enad.io/apis/auth/latest; status current; surface auth-api; reference /swagger/auth-api.json; Endpoint paths, methods, parameters, request bodies, responses, enums, and auth schemes must come from the Auth API OpenAPI reference.
- Asset library reads and DAM administration latest: https://docsv3.enad.io/media/dam/latest; status current; surface dam-api; reference /swagger/dam-api.json; Public asset-library read endpoint paths, methods, parameters, responses, enums, and auth schemes must come from the DAM API OpenAPI reference. DAM administration routes use the Management API OpenAPI reference.
- Integrations API latest: https://docsv3.enad.io/integrations; status current; surface integrations-api; reference /swagger/integrations-api.json; Use the Integrations API OpenAPI reference for endpoint paths, methods, parameters, request bodies, responses, enums, and auth schemes.
- DAM / Media API latest: https://docsv3.enad.io/media/latest; status current; surface media-api; reference /media/latest; Media CDN host generation, app-level image-proxy allowlist behavior, import/upload fallback, image transformations, image-delete cleanup, and cache-purge requests are defined behavior. Cache-key construction, cache retention, and edge freshness timing are not public contract details.
- Search GraphQL latest: https://docsv3.enad.io/search/latest; status current; surface search-graphql; reference /graphql/search-schema.graphql; Search GraphQL reference owns current root fields, operation names, variables, fragments, nullability, input fields, object fields, enum values, and product-query validation truth. Use /graphql/search-schema.graphql, /graphql/search-documents.graphql, and /reference/search-graphql/latest for public reference truth.
- Events latest: https://docsv3.enad.io/events/latest; status current; surface events-catalog; reference /events/catalog; Event type strings, base event envelope fields, payload schema IDs, and top-level payload fields are documented in Event catalog. Webhook delivery behavior and configured custom-header authentication are documented in Events latest. Nested payload details remain JSON Schema contract truth.

When a track is marked pending, use it only for route selection until the matching reference is available.

## Route readiness

- Start, SDKs, APIs, Search, Media, Events, Integrations, Agent guides, Reference, and Blog routes are present.
- Use route guides for orientation and the matching SDK, API, Search, Media, Events, or package reference for exact names, fields, and behavior.
- Use /ai/manifest.json when a tool needs structured route and version-track metadata.

## Version track rule

Docs uses per-surface version tracks. A track belongs to one package or API contract family, not to the whole docs site. `latest` is a moving alias for the current recommended track of that surface.

## Required reference boundary

Use Enad docs for guidance and route selection. Use SDK package reference and API/OpenAPI reference for exact SDK exports, component props, API fields, package versions, and runtime behavior. Do not copy live playground internals into apps.

## Included guidance

This bundle includes agent guidance for React SDK, TypeScript SDK, APIs, Search, playground boundaries, and theme restoration.
