skills.rest
Pieverse-Eng
Pieverse-EngOFFICIAL
Explore all skills by this author →
Website𝕏@pieverse_ioGitHub

pieverse-a2a

Probe Pieverse A2A HTTP 402 challenges, authorize wallet payments, and retry requests.

3|Updated Apr 15, 2026
Search Tags:#authorization#payment#http#wallet#a2a#402#pieverse
One-click install
npx skills add https://github.com/Pieverse-Eng/purrfect-skills --skill pieverse-a2a
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pieverse-a2a
Source: https://github.com/Pieverse-Eng/purrfect-skills/tree/main/pieverse-a2a
Command: npx skills add https://github.com/Pieverse-Eng/purrfect-skills --skill pieverse-a2a

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about pieverse-a2a

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle an HTTP 402 paymentRequired response from a Pieverse-gated API?▼

To handle an HTTP 402 paymentRequired response, the Skill probes the merchant URL, parses the challenge details like amountBaseUnits and chainId, and guides the user through wallet authorization to retry the request with a payment credential.

What do I need to configure to automate A2A payment authorization for HTTP resources?▼

Automating A2A payment authorization requires a hosted runtime environment configured with WALLET_API_URL, WALLET_API_TOKEN, and INSTANCE_ID to successfully call the platform wallet endpoint and extract payment credentials.

How does an agent retry an HTTP request after obtaining a Pieverse payment credential?▼

The agent retries the original HTTP request by preserving the initial method, headers, and body while inserting the extracted payment credential into the X-Pieverse-Payment header to access the gated merchant resource.

Can I dispute an incorrect merchant response during a Pieverse A2A payment flow?▼

Yes, you can dispute an incorrect merchant response by submitting a strict-mode challenge to the wallet challenge endpoint, which verifies the delivered result and attempts to resolve the payment discrepancy.

What specific details are parsed from a Pieverse 402 challenge body before requesting user payment confirmation?▼

The Skill parses required fields from the Pieverse 402 challenge body including challengeId, recipient, amountBaseUnits, token, and chainId to present accurate payment details for explicit user approval.

Related Skills

Explore More Software Engineering Skills→
CaptainCrouton89CaptainCrouton89
497

Vercel CLI Management

Automate Vercel deployments, environment variables, logs, and cron configuration.

Community
Intermediate
AradotsoAradotso
4

stripe-link-cli

Retrieve one-time Stripe Link payment credentials for agent-driven checkouts.

Official
Advanced
joshka0joshka0
3

foxctl OpenAPI

Plan and validate HTTP requests against OpenAPI specifications in dry-run mode.

Community
Basic
SignmanalSignmanal
1

mpp-agent

Automate HTTP 402 payment processing for MPP-compliant APIs.

Community
Intermediate