Most Enad implementation work starts with the same question: which surface should own this job? The fastest path is to choose by intent, then move to the page that matches the runtime you are working in.

Start with the job

• Use the React SDK when you are building storefront UI, account flows, themeable components, or checkout-adjacent customer experiences.
• Use the TypeScript SDK when server code, scripts, jobs, or backend services need a typed Enad client.
• Use Search when the feature needs product discovery, facets, autocomplete, or storefront search behavior.
• Use APIs and Reference when you need endpoint-level request and response details.
• Use Media when the work involves images, DAM, asset delivery, or media URLs.
• Use Events when the task is about webhooks, integrations, sync behavior, or downstream automation.
• Use Playground when you need to try a flow before wiring it into an app.

Give agents focused context

When an agent is helping with Enad work, give it the narrowest context that matches the task:

• Start with /llms.txt for a short routing index.
• Use /llms-full.txt when the task spans multiple Enad areas.
• Use /ai/manifest.json when the agent needs structured route data.
• Prefer the route-specific agent guides under Agent guides for SDK, API, Search, and prompt work.

Good default path

For a new storefront feature, begin with React SDK latest, add Search latest if discovery is involved, and use Reference only when endpoint details are needed.

For backend or automation work, begin with TypeScript SDK latest, then move to APIs, Events, or Media depending on the system you are integrating.