Clarify AgentPay MCP x402 payment controls#1
Open
up2itnow0822 wants to merge 2 commits into
Open
Conversation
3c22881 to
efca96d
Compare
a4bea12 to
440f9b3
Compare
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.
Purpose
Clarify the existing AgentPay MCP registry entry so buyers understand it as a non-custodial x402 payment-control layer, not a managed wallet or broad custody provider.
Market signal
Machine-payment directories are becoming a discovery surface for paid APIs, MCP payment tools, x402, MPP, stablecoins, and agent payment infrastructure.
Change
Updates the
agentpay-mcpdescription from:Non-custodial x402 MCP payment layer for AI agentsto:
Non-custodial x402 MCP payment controls for AI agents, with approval gates, spend caps, and receipt loggingValidation
agentpay-mcpalready exists inregistry.jsonunder Community Projects / MCP Bridges.python3 -m json.tool registry.jsonsuccessfully.