One product in three parts
Every InFlow transaction has an agent side and a seller side.
Pay as an agent
You build or operate an agent. Install the CLI, log in, and pay for your first resource.
Integrate your service
You operate an API or a service. Integrate InFlow in three steps: Payments, Enrollment, and Discovery.
Latest versions
| Component | Package | Latest |
|---|---|---|
| InFlow CLI | Install the CLI |  |
| Node.js seller, MPP | @inflowpayai/mpp-seller |  |
| Node.js seller, x402 | @inflowpayai/x402-seller |  |
| Node.js buyer, MPP | @inflowpayai/mpp-buyer |  |
| Node.js buyer, x402 | @inflowpayai/x402-buyer |  |
| Python SDK | inflowpay |  |
| Go SDK | github.com/inflowpayai/inflow-go |  |
| Rust SDK | inflow-* crates |  |
How it works
At runtime, an agent uses the three parts in this order.1
Discover
The agent searches a directory for services. It then reads what a service offers.
2
Enroll
The agent enrolls with the service and gets its own credential.
3
Pay
The service responds with HTTP
402 Payment Required. The agent pays, and the service returns the resource.InFlow Payments
InFlow Payments accepts MPP and x402. Integrate both. Both use HTTP402 and run side by side in one service.
- MPP (Machine Payments Protocol) accepts stablecoins and cards. It also supports subscriptions.
- x402 accepts stablecoins and linked cards. The agent pays onchain or from its InFlow balance.
402 response lists the accepted options, and the agent pays with one of them. See Payments with MPP and x402.
Environments
Every API key belongs to one environment.
Build in the sandbox first. To move to production, see Go live.
Get help
Discord
Ask the InFlow team and other builders.
GitHub
Read the source and the examples for the CLI and the Node.js SDK.
Write to info@inflowpay.ai.