Choose how you build
Build with a coding agent
The agent plans the integration with you and builds one approved step at a time.
Build with the documentation
Follow the steps below. Each step links to a full guide.
Integrate InFlow in three steps
Build in this order. When you build Discovery last, the ODP descriptions match the finished behavior of your service. You can add the steps one at a time. First, create a Seller account. Your service gets and manages agent payments with this account.1
Step 1: Payments
Integrate both MPP and x402 with the InFlow seller SDKs for Node.js, Python, Go, or Rust. Protect the paid operations that you choose. Keep your existing authentication and permissions.Start with the Payments quickstart. The protocol specifications are at mpp.dev and x402.org.
2
Step 2: Enrollment
Publish the AEP Service Document at
/.well-known/aep. Implement the enrollment commands that you advertise. See Enable agent enrollment.3
Step 3: Discovery
Publish the ODP Service Document at
/.well-known/odp. Declare only the catalog operations that you implement. See Make your products discoverable.Launch
Advertise only the capabilities that work. The admission checks of the directory apply to all advertised capabilities.1
Go live
Move from the sandbox to production. The directory reads only public documents. See Go live.
2
Check your integration with the InFlow CLI
Inspect your canonical origin. Then test discovery, enrollment, and each payment protocol against the running service.An
inspect result alone does not prove that these flows work. See Check your integration.3
Validate your service
Run the blocking checks that the directory runs at publication. See Validate the service.
4
Submit your service origin
Submit the canonical HTTPS origin that serves your ODP document. See Submit the service.