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 APIs become usable on demand. ## Core Features & Use Cases - Client Selection Guidance: Chooses between link-cli (Stripe Link), Tempo Wallet, Privy Agent CLI, AgentCash, and mppx based on the 402 challenge method and the user's funded wallet. - mppx Fast Path: Installs mppx via npm, creates an account, probes the merchant's 402 challenge with curl, and pays the request with automatic challenge/credential handling. - Pitfall Handling: Covers multi-method www-authenticate headers, zero-amount proof challenges, and Stripe-vs-Tempo method mismatches. - Use Case: A merchant API returns HTTP 402 with a www-authenticate: tempo header. The agent installs mppx, creates an account, and runs mppx <url> to pay and retrieve the actual response. ## Quick Start Ask the agent to pay the HTTP 402 challenge on a given URL using mppx and return the merchant's response.