a2a/x402: add AP2 mandate foundation for agent payments
Open
Nobody has claimed this yet.
codex
enhancement
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 2.4k
- Avg merge
- 1h 7m
- Merged PRs (30d)
- 23
Description
Goal
Add an opt-in AP2 mandate foundation so agents can carry auditable payment authorization over A2A and settle over x402 without changing defaults.
Scope
- Define minimal Checkout Mandate and Payment Mandate data structures with signing/verification helpers.
- Attach verified mandate metadata to A2A/x402 payment flows behind explicit options.
- Preserve current public defaults and avoid broad API breakage.
- Include docs/example notes only where needed to make the flow discoverable.
Acceptance criteria
- Unit tests cover mandate creation, signing, verification failure, and x402 rail metadata.
- A focused integration or gateway test shows an A2A request carrying mandate metadata into a paid-tool path.
- go test ./... passes.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing A2A payment flow and x402 rail integration; the issue does not name specific files or entry points. Define the mandate structures and signing behavior, then add unit coverage for creation, verification failure, and rail metadata. Confirm an integration or gateway test carries mandate metadata into a paid-tool path, and run go test ./....
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ai, distributed-systems, payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100