PipRail
Official<div align="center">
<img src="site/public/og.png" alt="PipRail — the payment layer for the agent economy" width="840" />
<br/>
<br/>
[](https://www.npmjs.com/package/@piprail/sdk)
[](https://www.npmjs.com/package/@piprail/mcp)
[](https://www.npmjs.com/package/@piprail/sdk)
[](LICENSE)
[](https://x402.org)
[](https://docs.piprail.com/chains/overview/)
[](https://github.com/piprail/piprail)
[](https://x.com/piprailhq)
**Let any HTTP endpoint charge for itself, and any agent pay for itself — across every major chain, in a couple of lines.**
[Website](https://piprail.com) · [Documentation](https://docs.piprail.com) · [npm](https://www.npmjs.com/package/@piprail/sdk)
</div>
---
PipRail implements the open [x402](https://x402.org) **"402 Payment Required"** standard with **no backend, no database, no account, no API key, and no fee**. Payments settle **straight into your wallet**, verified locally against your own RPC — across every major EVM chain plus **Solana, TON, Tron, NEAR, Sui, Aptos, Algorand, Stellar & the XRP Ledger**. Self-custodial throughout.
## How a payment moves
<div align="center">
<img src="site/public/flow.png" alt="How a payment moves — the full life of one payment, side by side. Left, the traditional MPP path (Stripe + Tempo): the agent's money is held in transit through a processor and a permissioned chain across roughly five hops, takes ~T+2 days to become spendable, and can be frozen or reversed. Right, PipRail's x402 wallet-to-wallet rail: the agent pays the merchant's wallet directly in a single on-chain transaction, the merchant gate verifies it locally, funds are spendable in seconds, there's no custodian, and the fee is 0%." width="840" />
<sub>**The middle is the difference.** A traditional processor holds the money in transit, takes days to release it, and can freeze or reverse it. PipRail removes the middle entirely — the agent pays the merchant's wallet directly, the merchant verifies it locally against their own RPC, and it settles in one transaction at **0% fee**, self-custodial end to end. <a href="https://piprail.com">See it on piprail.com →</a></sub>
</div>
## 📊 The pitch deck
<div align="center">
<a href="PipRail-deck.pdf"><img src=".claude/skills/branding/design/deck/preview/slide-01.png" alt="PipRail pitch deck — the universal payment rail for the agent economy. Click to open the full 16-slide PDF, rendered right here in your browser." width="840" /></a>
### ▶︎ [**Open the full deck — PDF**](PipRail-deck.pdf) ◀︎
<sub>Opens **right here in your browser** — no download, GitHub renders it inline. 16 slides · every stat sourced in the speaker notes.</sub>
</div>
The whole thesis in one read: **why** agent payments are happening now, **why** chain & token fragmentation is the enemy, and **how** a single `chain:` parameter turns PipRail into the universal adapter. The payment path is **0% forever** — the moat *and* the distribution; value accrues to the layer around the free rail, never the rail itself.
<details>
<summary><b>What's inside — the 16-slide arc</b></summary>
<br/>
| # | Slide | # | Slide |
|---|---|---|---|
| 1 | **Hero** — the universal payment rail for the agent economy | 9 | **The MCP** — give your agent a budget-bound wallet |
| 2 | **Why now** — money is moving on-chain | 10 | **Open · dual-rail · gasless** |
| 3 | **The new buyer** — autonomous agents | 11 | **MPP vs PipRail** — count the middlemen |
| 4 | **The standard** — x402, "402 Payment Required" | 12 | **Discovery + integrations** |
| 5 | **The problem** — chain & token fragmentation | 13 | **Why PipRail wins** — the moat |
| 6 | **The reveal** — the universal adapter | 14 | **Traction** |
| 7 | **How it works** — 402 → pay → verify → 200 | 15 | **Business model** — open core, 0% rail |
| 8 | **Two sides, one SDK** — accept *and* pay | 16 | **The ask** |
<sub>Source `.pptx` (fully editable, brand fonts embedded) lives in [`.claude/skills/branding/design/deck/`](.claude/skills/branding/design/deck/). The root `PipRail-deck.pdf` is regenerated from it — don't hand-edit the PDF.</sub>
</details>
> ### 📖 Full documentation → **[docs.piprail.com](https://docs.piprail.com)**
> The single, searchable **source of truth** — every function, option, chain, and example. This README is just the front door.
## What's here
| | |
|---|---|
| **[`@piprail/sdk`](https://www.npmjs.com/package/@piprail/sdk)** | The TypeScript SDK — accept & make x402 payments. The product. Optionally [swaps tokens](https://docs.piprail.com/making-payments/swapping/) where an open, keyless route exists (no fee, no API key, never automatic). |
| **[`@piprail/mcp`](https://www.npmjs.com/package/@piprail/mcp)** | An MCP server giving any AI agent a budget-bound wallet ([`io.github.piprail/mcp`](https://registry.modelcontextprotocol.io)). |
| **[`@piprail/create`](https://www.npmjs.com/package/@piprail/create)** | `npm create @piprail` — scaffolds a runnable, mainnet-by-default x402 merchant in one command. Paste a public address; no key, no backend. |
| **[`integrations/`](integrations)** | First-party agent-framework integrations — **OpenClaw**, **Hermes**, **elizaOS** (`@piprail/elizaos-plugin`), **n8n** (`@piprail/n8n-nodes-piprail`) & **Mastra**. Each wraps `@piprail/sdk` or `@piprail/mcp`; nothing new to build. |
| **[`site/`](site)** · **[`docs/`](docs)** · **[`examples/`](examples)** | [piprail.com](https://piprail.com) · the [docs.piprail.com](https://docs.piprail.com) source · runnable demos. |
## Quick taste
```bash
npm install @piprail/sdk viem
```
```ts
import { requirePayment } from '@piprail/sdk'
app.get('/report',
requirePayment({ chain: 'base', token: 'USDC', amount: '0.05', payTo: '0xYourWallet…' }),
(_req, res) => res.json({ report: 'TOP SECRET' }),
)
```
That route now costs **0.05 USDC on Base**, paid straight to your wallet. Point an agent at it and it pays itself — name any chain with a single `chain:` parameter. The full quickstart, every chain, the MCP server, spend controls, and the error model are in the **[docs](https://docs.piprail.com)**.
## Documentation & links
- **[docs.piprail.com](https://docs.piprail.com)** — the complete manual (source of truth)
- **[MCP server](https://docs.piprail.com/mcp/overview/)** · **[Discovery](https://docs.piprail.com/discovery/discover-and-register/)** · **[Supported chains](https://docs.piprail.com/chains/overview/)**
- **[Integrations](https://docs.piprail.com/integrations/)** — drop PipRail into agent frameworks: [OpenClaw](integrations/openclaw/piprail), [Hermes](integrations/hermes/piprail), [elizaOS](integrations/elizaos/piprail), [n8n](integrations/n8n/piprail) & [Mastra](integrations/mastra/piprail) (more coming)
- **[Runnable examples](examples)** — merchant + agent demos, a live Anvil end-to-end, and the [`why-402`](examples/basics/why-402/) teardown
- **[Releasing](RELEASING.md)** (tag-driven CI) · **[Contributing](CONTRIBUTING.md)** (DCO)
## Spread the word
PipRail is free, open-source, and has no backend to sell you — so word of mouth is how it grows. If it saved you from building a payments backend, the best way to give back is to help other developers (and their agents) find it:
- ⭐ **[Star PipRail on GitHub](https://github.com/piprail/piprail)** — the #1 way to help others discover it
- 𝕏 **[Follow @piprailhq](https://x.com/piprailhq)** — new chains, ship logs, and agent-payment tips
- 🌐 **[piprail.com](https://piprail.com)** · 📖 **[docs.piprail.com](https://docs.piprail.com)**
## License & trademark
**Code:** [MIT](LICENSE) — use it, fork it, ship it, commercially or otherwise.
**Name & brand:** **PipRail™**, the logo, and the `@piprail` npm scope are trademarks of the PipRail project — MIT covers the *code*, not the *name*. Build on it freely; just don't call a fork "PipRail" or imply it's official. See [TRADEMARK.md](TRADEMARK.md).
<div align="center">
<br/>
<img src="site/public/logo.png" alt="PipRail" width="64" />
<sub>Built for the agent economy · <a href="https://piprail.com">piprail.com</a></sub>
</div>
TDQS
Scored across 8 tools
Each tool targets a distinct stage of the x402 workflow: discovery, quoting, planning, paying, registration, budget checking, guidance, and receipt verification. There is no functional overlap between tools, making selection straightforward for an agent.
All tools share the piprail_ prefix and follow a consistent verb or verb_noun pattern in snake_case (e.g., quote_payment, pay_request, verify_receipt). The naming is predictable and reinforces the tool's purpose.
With 8 tools, the server is well-scoped. Each tool covers a necessary function for both buyers and sellers in the x402 payment ecosystem, with no apparent redundancy or bloat.
The buyer lifecycle is fully covered from discovery through payment and verification, with budget and guide support. The only minor gap is the lack of explicit update or unregister functionality for seller resource listings, but this is likely outside the core client scope.