Repository navigation
docs(x402): example of x402 sign with a plain HTTP x402 endpoint - #465
Merged
Merged
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.
I use
mcpcas my x402 wallet. I wanted to pay a plain HTTP x402 v2 endpoint (not an MCP server) with it, andx402 signdoes the job well. The README just doesn't show that flow, so this PR adds a short example under "Manual payment signing". It is docs only, with no endpoint named.How I tested it (@apify/mcpc@0.7.0 from npm, a wallet imported with
mcpc x402 import):exactUSDC endpoint on Base mainnet (eip155:8453, 0.01 USDC): the server returned 200, and itsPAYMENT-RESPONSEreported success. Settlement tx: https://basescan.org/tx/0x4059242169212737b0f32ee4136153db9857de8863ab511fe9e0c2451ba1be5bsign→ retry flow on a second Base endpoint (0.002 USDC,POSTwith a JSON body), and it settled too: https://basescan.org/tx/0x95c5eec65473b16a3b9ea3f395e52b5f566cbbee3ac0086419e805960f8b35dcHappy to trim it, or move it to the skill doc if you prefer.