// GLOSSARY -- X402
What is the A2A x402 Extension?
Combines Google's Agent-to-Agent protocol with x402 payments — agents communicating via A2A settle payments using HTTP-native x402 flows.
WHY IT MATTERS
A2A defines communication; x402 defines payment. The extension connects both for the full cycle: discover via A2A, negotiate, pay via x402.
Creates a complete commerce stack from complementary standards. Neither alone is sufficient.
Handles the task-to-payment handoff for seamless A2A ecosystem transactions.
HOW POLICYLAYER USES THIS
PolicyLayer enforces policies on A2A x402 transactions — validating both communication context and payment parameters.
FREQUENTLY ASKED QUESTIONS
Do I need both protocols?
For the full agent commerce flow (discover + pay), yes. For payments only, x402 alone works. For task delegation without payment, A2A alone works.
Which agents support this?
Any agent implementing both A2A and x402 standards. The extension is designed to be framework-agnostic.
Is this production-ready?
The individual protocols (A2A, x402) are maturing. The extension connecting them is newer and still evolving.