Integrations
PipRail works today as a standalone SDK: gate a server route with requirePayment, pay as a client with PipRailClient, or hand an agent a budget-bound wallet via the MCP server, across every supported chain.
These pages cover first-party integrations that drop PipRail into the frameworks where agents already live, without writing payment code.
Available
Section titled “Available”| Integration | What it gives you |
|---|---|
| OpenClaw | A ClawHub skill that hands an OpenClaw agent the full set of PipRail tools (budget-bound), via @piprail/mcp. |
| Hermes | A Hermes MCP catalog entry (and Skills Hub skill). Add one mcp_servers block and the agent gets the full set of PipRail tools, budget-bound. |
| elizaOS | A native elizaOS plugin (@piprail/elizaos-plugin) that wraps @piprail/sdk’s paymentTools as six budget-bound agent actions (pay / quote / plan / discover / budget / guide). Add piprailPlugin to your character; no MCP server needed. |
| n8n | A native n8n community node (@piprail/n8n-nodes-piprail). Pay / plan / quote / estimate an x402 URL from any workflow, callable by n8n AI Agent nodes and budget-bound. Install via Settings → Community Nodes. |
| Mastra | The first x402 integration for Mastra. Wire @piprail/mcp in via Mastra’s MCPClient and an agent gets the full set of PipRail tools, budget-bound. viem never enters Mastra’s tree. |
More framework integrations are on the way. Any MCP client can use PipRail today via the MCP server; see Client setup.