What problem does it solve? When an API responds with HTTP 402 Payment Required, most agents can only log the failure. This Skill lets the agent actually pay per-request for API access using Machine Payments Protocol (MPP) clients, so paid merchant endpoints become usable without manual wallet handling. ## Core Features & Use Cases - Multiple MPP clients: Choose between mppx, Tempo Wallet, Privy Agent CLI, AgentCash, or Stripe Link depending on the 402 challenge method and the user's funded wallet. - Challenge inspection: Probe merchant URLs with curl to confirm they speak MPP and decode the www-authenticate header before paying. - Automated payment flow: mppx handles the 402 challenge/credential exchange automatically and prints the merchant's actual response, with receipt verification via verbose mode. - Use Case: A user hits a paid data API that returns HTTP 402 with a Tempo challenge. The agent installs mppx, creates an account, pays the request, and returns the API response with its payment receipt. ## Quick Start Ask the agent to pay for and fetch a URL that returned HTTP 402 Payment Required using mppx.