Add PipRail to Crypto payment rails - #38
Open
John-Weeks-Dev wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds PipRail under Crypto payment rails, in the same shape as the existing Fewsats entry: a maintained open source toolkit for one of the rails already covered, rather than a new protocol.
PipRail is an MIT-licensed TypeScript SDK for x402. A server can charge for a request and an AI agent can pay for one, across 29 chains in 10 families. Verification runs against the developer's own RPC node, so there is no backend and no fee in between. It also ships an MCP server that hands any MCP client a budget-bound wallet.
I maintain it, so these are official sources per CONTRIBUTING.md.
On the link check: every link added returns 200. I deliberately left out the npm package pages (npm serves 403 to automated checkers) and our live 402 demo endpoint (it returns
402 Payment Requiredby design, which a link checker reads as a failure).Changes are the section itself plus one matching line in Contents. Happy to reshape or trim it if you would rather it sat somewhere else.