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

# The InFlow directory

> The InFlow directory lists services that agents can buy from with InFlow. Agents and people search it to find services.

The InFlow directory is a catalog of B2AI services that agents can buy from with InFlow. It lists services for inference, compute, data APIs, storage, observability, and more. [Discovery](/concepts/discovery) starts here.

People read the directory at `directory.inflowpay.ai`. Agents search it with `inflow directory search`. See [Search the directory](/agents/discover-and-enroll#search-the-directory).

## What a listing shows

| Field | Meaning |
| - | - |
| Name | The name of the service or the collection. |
| Category | One category, for example Sales Intelligence, Web Search, or Compute. |
| Protocols | The protocols that the listing advertises, for example ODP, AEP, MPP, x402, MCP, OpenAPI, or TAP. |
| Description | One sentence about what the service does. |
| Available through | The service that sells it. A collection shows its parent service. A resold API shows the reseller. |

A listing is a service or a collection. A collection is a group of related offerings inside one service. One service can have several collections.

The same API can have more than one listing, for example from the provider and from a reseller. Check **Available through** before you choose.

## Filters

| Filter | Values |
| - | - |
| Category | The kind of service, for example AI Models, Compute, Data & Research, Payments, Sales Intelligence, or Web Search. |
| Protocol | AEP, MCP, MPP, ODP, OpenAPI, TAP, and x402. |
| Network | The payment networks, for example InFlow, Base, Solana, Card, Stripe, and Tempo. |

## Read the directory from code

The directory has a public API that needs no account and no key. Use it to copy the list of ODP services into your own platform. See [Read the directory from code](/reference/directory-api).

## How a service gets listed

A seller submits the origin of the service. The directory reads and validates its public ODP Service Document or its JSON OpenAPI 3.x document. Then it lists the service. See [Publish to the directory](/sellers/publish-to-the-directory).

The directory checks each listing again over time. A listing shows when the directory last checked it.


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