Quick start

Integrate AEP with a coding agent

Choose what your application needs, review a repository assessment, and approve a plan before implementation begins.

Start in your repository

Open your application repository in your coding agent and copy this prompt into its chat. The guide supports Go, Java, Node.js, Python, and Rust. If you are unsure which SDK fits, the coding agent can recommend one after examining your application.

Read https://www.aep.foundation/integration.md
and follow its guided process
to integrate AEP into this repository.

Begin with the introduction. Pause at each stage
and wait for my response before continuing.

You can read the integration guide before starting. The coding agent needs access to the guide and your repository to perform the assessment.

Choose what you are building

The coding agent helps you write the integration. Your application can act as an AEP Agent, an AEP Service, or both. The interview establishes which responsibilities your application needs.

Agent application: Call AEP-enabled Services, inspect their requirements, enroll, check status, and manage supported session credentials.
Service: Accept Agents, publish enrollment requirements, verify requests, apply access policy, and optionally issue session credentials.

Building both sides

If you need both, the plan separates the work into independently reviewed tasks. Using a hosted identity provider is a further choice when relevant; operating an identity Platform is not automatically part of either path.

Review the assessment and plan

Once you confirm the repository, the coding agent keeps your answers and findings in an integration-plan file. It examines the application without changing code, proposes the Agent access to support, and resolves the remaining design choices with you. It then completes the implementation plan for your approval. The file is updated before each handoff so you can resume in another session.

Implementation proceeds one task at a time. Each handoff explains what changed, which checks ran, and what comes next. Type go to continue or provide corrections first. Deployment and publication require separate approval.

Keep related integrations separate

The assessment checks existing ODP and MPP/x402 integrations so AEP can coexist with their request handling. This workflow does not build discovery or payments. Their absence does not prevent an AEP integration.

Planning another integration

If you plan to add either, you can continue with the application's current capabilities or pause for the separate ODP or InFlow Payments workflow.

Return as your application grows

Use the same prompt when you add session credentials, payments, a hosted identity provider, or the other side of AEP. The coding agent reassesses the current code and plans only the changes needed for your goals. An earlier plan is helpful but is not required.