What problem does it solve? APIs that return HTTP 402 Payment Required block normal requests until a payment credential is attached. This Skill lets an agent actually pay those per-request charges using Machine Payments Protocol (MPP) clients instead of just logging the 402 response. ## 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 and payment: Probe a URL with curl to confirm it speaks MPP, then pay the request and verify the receipt header. - Use Case: A merchant API returns HTTP 402 with a www-authenticate: tempo header. Install mppx, create an account, and run mppx <url> to complete the payment handshake and receive the actual API response. ## Quick Start Install mppx globally with npm, create an account, then run mppx against the URL that returned the 402 challenge to pay and retrieve the response.