Add fail-closed Agent Guild policy for x402 payments - #369
Open
AgentTanuki wants to merge 1 commit into
Open
Conversation
AgentTanuki
marked this pull request as ready for review
August 12, 2026 21:38
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.
Summary
--x402-policy agent-guild --x402-max-amount <atomic>Safety properties
--x402behavior is unchanged unless the policy flag is suppliedmcp://payment resources remain an explicit fail-closed compatibility boundary because AGPD-1 currently requires an HTTP(S) resourceThe policy decision is itself a paid x402 call, so the wallet needs Base USDC for the decision and protected tool call.
Validation
git diff --checkNo live payments were made while implementing or testing this change.