Agentic Payments

Pay HTTP 402-protected resources on the user's behalf. InFlow speaks two payment protocols — MPP and x402 — but the flow is the same for both: shared setup (install, run, authenticate), then a router that picks the protocol from the seller's 402 header, then one Paying a 402 resource section that covers both. A per-protocol delta table at the top of that section lists the handful of real differences (header name, credential name, filters, error codes); read your row, then follow the shared steps.

Installing

Install with npm install -g @inflowpayai/inflow. Or run directly with npx @inflowpayai/inflow.

Running

InFlow runs as a standalone CLI or an MCP server.

MCP: add an inflow server to your MCP client config that runs npx -y @inflowpayai/inflow --mcp. Keep the -y flag — it suppresses npx's confirmation prompt, without which the MCP host can stall on first run.

MCP mode exposes every CLI command as a tool. Call tools/list on the MCP server for the authoritative inventory; arguments mirror the CLI flags one-to-one.

Common commands / options

The CLI is the source of truth for exact flags, enums, and output shapes — run inflow <command> --schema for one command, or inflow --llms-full for everything. This playbook covers when and why, not exhaustive parameter lists; when you need a precise flag name, value set, or response shape, query the CLI rather than guessing.