> ## Documentation Index
> Fetch the complete documentation index at: https://ifdocdemo.lumivescence.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrate your service

> Integrate InFlow in three steps: Payments, Enrollment, and Discovery. Then launch your service and publish it in the InFlow directory.

InFlow is one product with three parts. A seller integrates them in three steps, then launches.

| Step | Part | Open standard | What it lets an agent do |
| - | - | - | - |
| 1 | Payments | MPP and x402 | Pay for the paid operations of your service. |
| 2 | Enrollment | AEP | Enroll, authenticate, and get credentials for ongoing access. |
| 3 | Discovery | ODP | Find your products, read their details, and find the actions to use or buy them. |

## Choose how you build

<CardGroup cols={2}>
  <Card title="Build with a coding agent" icon="wand-magic-sparkles" href="/sellers/integrate-with-a-coding-agent">
    The agent plans the integration with you and builds one approved step at a time.
  </Card>

  <Card title="Build with the documentation" icon="book" href="#integrate-inflow-in-three-steps">
    Follow the steps below. Each step links to a full guide.
  </Card>
</CardGroup>

## 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](/sellers/create-a-seller-account). Your service gets and manages agent payments with this account.

<Steps>
  <Step title="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](/sellers/get-started). The protocol specifications are at [mpp.dev](https://mpp.dev) and [x402.org](https://x402.org).
  </Step>

  <Step title="Step 2: Enrollment">
    Publish the AEP Service Document at `/.well-known/aep`. Implement the enrollment commands that you advertise. See [Enable agent enrollment](/sellers/enable-enrollment).
  </Step>

  <Step title="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](/sellers/make-products-discoverable).
  </Step>
</Steps>

## Launch

Advertise only the capabilities that work. The admission checks of the directory apply to all advertised capabilities.

<Steps>
  <Step title="Go live">
    Move from the sandbox to production. The directory reads only public documents. See [Go live](/sellers/go-live).
  </Step>

  <Step title="Check your integration with the InFlow CLI">
    Inspect your canonical origin. Then test discovery, enrollment, and each payment protocol against the running service.

    ```bash theme={null}
    inflow inspect https://api.example.com
    ```

    An `inspect` result alone does not prove that these flows work. See [Check your integration](/sellers/verify-your-integration).
  </Step>

  <Step title="Validate your service">
    Run the blocking checks that the directory runs at publication. See [Validate the service](/sellers/publish-to-the-directory#step-2-validate-the-service).
  </Step>

  <Step title="Submit your service origin">
    Submit the canonical HTTPS origin that serves your ODP document. See [Submit the service](/sellers/publish-to-the-directory#step-3-submit-the-service).
  </Step>
</Steps>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.