mpp-agent

Automate HTTP 402 Payment Required responses by using Machine Payments Protocol to programmatically initiate and complete API payments. The mpp-agent skill handles this process, including receipt verification and parsing multiple payment methods from the www-authenticate header.

Machine Payments Protocol (MPP) is used when API merchants return HTTP 402 Payment Required responses. You need MPP to programmatically execute payments for these API interactions, verify receipts, and handle multiple payment method options automatically.

Machine Payments Protocol client selection supports multiple options, including link-cli, Tempo Wallet, Privy Agent CLI, AgentCash, and mppx. This allows API payment processing to utilize various client libraries for different payment method requirements.

Verify API payment receipts through the Machine Payments Protocol by executing the payment for the HTTP 402 response. The mpp-agent skill includes built-in receipt verification and handles multiple payment methods specified in the www-authenticate header.

Node.js is required to process HTTP 402 Payment Required API responses using the mpp-agent skill. The Node.js environment executes the provided scripts to automate Machine Payments Protocol interactions and client library selection.

APIs return HTTP 402 Payment Required when merchants demand payment for resource access. MPP handles this by parsing multiple payment methods from the www-authenticate header and executing the transaction via supported clients like Tempo Wallet or mppx.