What problem does it solve? Merchant APIs increasingly respond with HTTP 402 Payment Required, and agents need a way to actually pay per-request charges instead of just logging the rejection. This Skill wraps Machine Payments Protocol (MPP) clients so an agent can complete the 402 challenge/credential flow and retrieve the paid response. ## Core Features & Use Cases - Multiple MPP clients: Choose between mppx, Tempo Wallet, Privy Agent CLI, AgentCash, or Stripe Link CLI depending on the challenge method and the user's funded wallet. - Challenge inspection: Probe a URL with curl to confirm it speaks MPP and decode the www-authenticate header before paying. - Automated payment flow: Run mppx against a URL to handle the 402 handshake automatically, including POST requests with JSON bodies and receipt verification. - Use Case: A user hits an API that returns HTTP 402 with a Tempo challenge. The agent installs mppx, creates an account, pays the request, and returns the merchant's actual response with the receipt header. ## Quick Start Ask the agent to pay the HTTP 402 charge on a given API URL using mppx and return the paid response.
