Back to Directory

Integrate your Service

Make your products discoverable, let agents enroll, and accept agent-native payments to publish your Service in the B2AI Directory.

Build with a coding agent

Instead of working through the documentation yourself, start a guided coding-agent session in your repository. Your agent will ask about your goals, investigate the application, and help you plan, implement, and verify the integration.

Integrate with a coding agent

Or build with the documentation

Follow these documentation links to implement the integrations yourself, using the steps below. Prefer guided help in your repository? Start the coding-agent flow beneath these links.
MPPx402

Payments

Use the InFlow Node seller SDK to protect purchase endpoints with MPP or x402. Supporting either protocol satisfies the payment requirement; supporting both gives agents more choice.InFlow Documentation
AEP

Enrollment and access

Publish an AEP Service Document so agents can enroll, authenticate, and receive credentials for ongoing access.AEP Documentation
ODP

Products and discovery

Publish an ODP Service Document and expose the catalog operations agents use to browse, search, inspect, and act on products.ODP Documentation

Publish your Service in seven steps

For the complete integration, build Payments, then AEP, then ODP before verification and publication. If you are focusing on a subset, skip unselected integrations and advertise only what works. Directory admission requirements still apply to publication.
1

Create an InFlow Seller account

Use an InFlow Seller account to receive and manage payments from agents that purchase from your Service.Create Seller account
2

Enable agent payments

Use the InFlow Node seller SDK to integrate MPP and x402, or choose one protocol. Supporting both gives agents more choice. Configure supported payment options and protect the selected paid operations while preserving existing authentication and permissions.
Protocol references:MPP protocolx402 protocol
3

Enable agent enrollment with AEP

Integrate an AEP Service SDK, publish the Service Document below, and implement the enrollment commands you advertise. Preserve your application's permissions and require authentication for protected operations, including paid operations that require an account.
/.well-known/aep
4

Make your products discoverable with ODP

Integrate an ODP Service SDK, publish the Service Document below, and declare only the catalog operations you implement. Describe your Offerings and Actions, including the authentication and payment behavior already available at their endpoints.
/.well-known/odp
5

Verify your integration with InFlow CLI

Install InFlow CLI and inspect your canonical origin. Check the capabilities you implemented, then verify discovery, enrollment, and each selected payment protocol against your running Service. Obtain approval and set spending limits before payment checks; an inspect result alone does not prove these flows work.Install InFlow CLI
inflow inspect https://api.example.com
6

Validate your Service integration

Run the same blocking checks used by directory publication, including ODP metadata, branding resources, advertised AEP support, and payment declarations. The results identify invalid documents, resources, and declarations before submission.Validate your Service
7

Submit your Service origin

Choose the canonical HTTPS origin that serves your ODP document. Submit the origin itself without a path, query, or fragment - not a well-known document or product URL. Its documents and declared endpoints must be publicly reachable.
Example originhttps://api.example.com
Submit from your browserUse the guided form to validate and submit your Service origin from the browser.Publish your Service
Submit through the APIAgents and automated workflows can submit the same Service origin directly to the directory API.
curl --request POST https://directory.inflowpay.ai/v1/services \
  --header 'Content-Type: application/json' \
  --data '{"origin":"https://api.example.com"}'

What happens after submission

Once listed, your Service becomes discoverable through InFlow CLI and the agents that use it. Agents can find your Offerings and follow the enrollment and payment capabilities your Service exposes.