Integrate ODP with a coding agent

Start in your repository

Open your application repository in your coding agent, then copy and paste this prompt into its chat. The guide supports Go, Java, Node.js, Python, and Rust. You can choose an SDK or ask the agent to recommend one after inspecting your application.

Read https://www.offeringprotocol.org/integration.md
and follow its guided process to integrate ODP 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.

Review each step

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 which capabilities to expose, and helps you select them. It then completes the implementation plan for your approval. The file is updated before each handoff so you can resume in another session.

Review the plan before approving implementation. Each task ends with the changes made, checks performed, and a specific next step. Type go when you are ready to continue, or provide corrections first. Deployment and directory submission require separate approval.

Keep the scope clear

Choose Minimal, Recommended, or Complete integration based on the discovery features your application needs. Each choice must meet the applicable ODP requirements; Complete means all relevant features, not every optional feature.

Existing AEP and MPP/x402 integrations are reflected in ODP. This workflow does not build them.

Return as your service grows

Use the same prompt after adding authentication, payments, or catalog features. The agent reassesses the current code and plans the changes needed for your new goals. A previous plan can help, but it is not required and does not replace inspecting the application.