> ## 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.

# Check your integration

> Test Payments, Enrollment, and Discovery against the running service before you publish it.

Check Payments, Enrollment, and Discovery against the running service before you submit it to the directory. This is the second page of Launch.

An `inflow inspect` result shows only what your service advertises. It does not prove that discovery, enrollment, or payment works.

## Two groups of checks

Your integration is complete only when both groups pass.

| Group | What it covers |
| - | - |
| Project checks | Your own tests, coverage, static analysis, and regression checks. |
| InFlow checks | InFlow CLI checks against the running service. For ODP, also the directory publication. |

Track five states separately: local tests pass, the running service passes, the service is deployed, the service is submitted, and the directory lists it. A submission does not prove a listing.

## Step 1: Install the CLI and log in

See [Install the CLI](/agents/install-the-cli) and [Authenticate](/agents/authenticate). Use the environment of the service that you test. Add `--sandbox` for a sandbox service.

## Step 2: Inspect the origin

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

Confirm that the output reports ODP, AEP, MPP, and x402. Confirm that it reports nothing that you did not build.

## Step 3: Check discovery

```bash theme={null}
inflow odp inspect https://api.example.com
inflow odp offerings list https://api.example.com
inflow odp offerings get https://api.example.com <offering-id>
```

Confirm that each offering has the fields of your discovery level. A paid offering needs a price and at least one action. For the price check, see [Make your products discoverable](/sellers/make-products-discoverable#step-5-check-discovery).

Follow the `next` link of each list to the last page. Each page must advance, and the last page must have no `next`. See [Return usable next links](/sellers/make-products-discoverable#return-usable-next-links).

## Step 4: Check enrollment

```bash theme={null}
inflow aep inspect https://api.example.com
inflow aep enroll https://api.example.com --interval 5
inflow aep fetch https://api.example.com/protected
```

See [Enable agent enrollment](/sellers/enable-enrollment#step-5-check-enrollment).

## Step 5: Check each payment protocol

<Warning>
  A payment check moves real money in production. Before each payment check, confirm the environment, the destination, the operation, and the spending limit. Get approval from the owner of the paying account.
</Warning>

Read the challenge first. These commands send a request but do not pay.

<CodeGroup>
  ```bash MPP theme={null}
  inflow mpp inspect https://api.example.com/api/widgets
  ```

  ```bash x402 theme={null}
  inflow x402 inspect https://api.example.com/api/widgets
  ```
</CodeGroup>

Then pay one endpoint with each protocol.

<CodeGroup>
  ```bash MPP theme={null}
  inflow mpp pay https://api.example.com/api/widgets --interval 5
  ```

  ```bash x402 theme={null}
  inflow x402 pay https://api.example.com/api/widgets --interval 5
  ```
</CodeGroup>

For the sandbox flow, see [Test a payment](/sellers/test-a-payment).

## Step 6: Check the full agent path

Run one full path as an agent does. Find an offering with ODP. Enroll with AEP. Then pay for the action of that offering. Get approval before the payment.

Pass the method and the body of the resolved request with `--method` and `--data`.

```bash theme={null}
inflow odp actions resolve https://api.example.com <offering-id> <action-id>
inflow aep enroll https://api.example.com --interval 5
inflow mpp pay <url-from-the-resolved-request> --interval 5
```

## Next step

<Card title="Publish to the directory" icon="globe" href="/sellers/publish-to-the-directory">
  Validate the service and submit its origin.
</Card>


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