接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
npx -y @piprail/[email protected]Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
PIPRAIL_PRIVATE_KEY=<secret> PIPRAIL_CHAIN=<value> PIPRAIL_CHAINS=<value> PIPRAIL_MAX_AMOUNT=<value> PIPRAIL_MAX_TOTAL=<value> PIPRAIL_MAX_TOTAL_DENOM=<value> PIPRAIL_MAX_PAYMENTS=<value> PIPRAIL_MAX_PAYMENTS_PER_WINDOW=<value> PIPRAIL_WARN_AT_FRACTION=<value> PIPRAIL_SPEND_LOG=<value> PIPRAIL_EVENT_LOG=<value> PIPRAIL_TOKENS=<value> PIPRAIL_SCHEMES=<value> claude mcp add io.github.piprail-mcp -- npx -y @piprail/mcp@0.10.0在終端機中執行。
{ "mcpServers": { "io.github.piprail-mcp": { "command": "npx", "args": [ "-y", "@piprail/[email protected]" ], "env": { "PIPRAIL_PRIVATE_KEY": "<secret>", "PIPRAIL_CHAIN": "<value>", "PIPRAIL_CHAINS": "<value>", "PIPRAIL_MAX_AMOUNT": "<value>", "PIPRAIL_MAX_TOTAL": "<value>", "PIPRAIL_MAX_TOTAL_DENOM": "<value>", "PIPRAIL_MAX_PAYMENTS": "<value>", "PIPRAIL_MAX_PAYMENTS_PER_WINDOW": "<value>", "PIPRAIL_WARN_AT_FRACTION": "<value>", "PIPRAIL_SPEND_LOG": "<value>", "PIPRAIL_EVENT_LOG": "<value>", "PIPRAIL_TOKENS": "<value>", "PIPRAIL_SCHEMES": "<value>" } } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
Let any HTTP endpoint charge for itself, and any agent pay for itself — across every major chain, in a couple of lines.
Website · Documentation · npm
PipRail implements the open x402 "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.
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. See it on piprail.com →
Opens right here in your browser — no download, GitHub renders it inline. 16 slides · every stat sourced in the speaker notes.
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.
Source .pptx (fully editable, brand fonts embedded) lives in .claude/skills/branding/design/deck/. The root PipRail-deck.pdf is regenerated from it — don't hand-edit the PDF.
📖 Full documentation → docs.piprail.com
The single, searchable source of truth — every function, option, chain, and example. This README is just the front door.
npm install @piprail/sdk viem
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.
why-402 teardownPipRail 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:
Code: MIT — 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.
Built for the agent economy · piprail.com
Budget-bound x402 payment wallet for AI agents — pays HTTP 402 URLs, capped locally. No backend.
{ "mcpServers": { "io.github.piprail-mcp": { "command": "npx", "args": [ "-y", "@piprail/[email protected]" ], "env": { "PIPRAIL_PRIVATE_KEY": "<secret>", "PIPRAIL_CHAIN": "<value>", "PIPRAIL_CHAINS": "<value>", "PIPRAIL_MAX_AMOUNT": "<value>", "PIPRAIL_MAX_TOTAL": "<value>", "PIPRAIL_MAX_TOTAL_DENOM": "<value>", "PIPRAIL_MAX_PAYMENTS": "<value>", "PIPRAIL_MAX_PAYMENTS_PER_WINDOW": "<value>", "PIPRAIL_WARN_AT_FRACTION": "<value>", "PIPRAIL_SPEND_LOG": "<value>", "PIPRAIL_EVENT_LOG": "<value>", "PIPRAIL_TOKENS": "<value>", "PIPRAIL_SCHEMES": "<value>" } } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
發布者列出了以下環境變數:PIPRAIL_PRIVATE_KEY, PIPRAIL_CHAIN, PIPRAIL_CHAINS, PIPRAIL_MAX_AMOUNT, PIPRAIL_MAX_TOTAL, PIPRAIL_MAX_TOTAL_DENOM, PIPRAIL_MAX_PAYMENTS, PIPRAIL_MAX_PAYMENTS_PER_WINDOW, PIPRAIL_WARN_AT_FRACTION, PIPRAIL_SPEND_LOG, PIPRAIL_EVENT_LOG, PIPRAIL_TOKENS, PIPRAIL_SCHEMES。
PipRail 透過 stdio 在本機執行。
上次檢查時間:2026-11-10。 Budget-bound x402 payment wallet for AI agents — pays HTTP 402 URLs, capped locally. No backend.