pieverse-a2a

What problem does it solve?

Enables an agent to access HTTP resources protected by Pieverse A2A payment challenges by automating the probe, user-confirmed wallet authorization, and retry flow needed to obtain gated merchant responses.

Core Features & Use Cases

• Probe and detect: Perform an initial request to the merchant, detect HTTP 402 responses carrying a Pieverse paymentRequired body, and parse required fields such as challengeId, recipient, amountBaseUnits, token, and chainId.
• Hosted wallet authorization: Guide the user to confirm payment, call the platform wallet authorization endpoint using WALLET_API_URL and WALLET_API_TOKEN, and extract the returned payment credential while supporting soft and strict verification modes.
• Retry and dispute: Retry the original request preserving method, body, and merchant headers with the payment credential in the X-Pieverse-Payment header, and optionally submit strict-mode challenges to the wallet challenge endpoint if the delivered result is incorrect.
• Use Case: When a merchant API returns a Pieverse 402, present the payment details to the user, obtain explicit approval, authorize payment through the hosted wallet, retry the request with the credential, and report both credential and final merchant response.

Quick Start

Use pieverse-a2a to probe the merchant URL, confirm the payment details with the user, authorize via the hosted wallet, and retry the request with the returned payment credential.