mpp-agent

Automate HTTP 402 Payment Required challenges using the Machine Payments Protocol.

Updated May 4, 2026
One-click install
npx skills add https://github.com/InverterNetwork/hermes-agent --skill mpp-agent-inverternetwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mpp-agent
Source: https://github.com/InverterNetwork/hermes-agent/tree/main/optional-skills/payments/mpp-agent
Command: npx skills add https://github.com/InverterNetwork/hermes-agent --skill mpp-agent-inverternetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mppx.

What problem does it solve?

This skill resolves the friction of accessing premium APIs that require payment via the Machine Payments Protocol (MPP) by automating the 402 Payment Required handshake.

Core Features & Use Cases

  • Automated Payment Handling: Automatically detects and satisfies HTTP 402 challenges from MPP-compliant services.
  • Multi-Client Support: Integrates with various wallets including Tempo, Privy, AgentCash, and mppx for flexible payment options.
  • Use Case: When an API returns a 402 error, the agent uses this skill to negotiate the payment and complete the request without interrupting your workflow.

Quick Start

Use the mpp-agent skill to pay for the API request at the provided URL using your configured mppx account.

Frequently Asked Questions about mpp-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate payments for HTTP 402 Payment Required API challenges?

To automate HTTP 402 Payment Required API challenges, you use an agent to automatically detect the challenge, negotiate the payment via the Machine Payments Protocol, and complete your request. This eliminates manual payment friction for premium APIs.

What is the Machine Payments Protocol for per-request API billing?

The Machine Payments Protocol (MPP) is a standard for per-request API billing that returns an HTTP 402 Payment Required challenge. It enables automated agents to negotiate and satisfy micro-payments for accessing premium API services without manual intervention.

Do I need a pre-funded wallet to handle 402 Payment Required responses?

Yes, you need a pre-funded wallet or account to handle 402 Payment Required responses. The automated payment process requires sufficient funds to execute transactions and satisfy the MPP challenge when accessing premium APIs.

Which wallet integrations support automated Machine Payments Protocol transactions?

Supported wallet integrations for automated Machine Payments Protocol transactions include Tempo, Privy, AgentCash, and mppx. These multi-client options provide flexible payment methods for satisfying HTTP 402 API challenges.

Does the Machine Payments Protocol agent work with Node.js environments?

Yes, the Machine Payments Protocol agent works with Node.js environments, specifically requiring Node.js version 20 or higher. This runtime environment is necessary to execute the payment transactions and handle the HTTP 402 challenge automation.

Why does my API request return a 402 error and how do I resolve it?

An API request returns a 402 error when the service requires payment via the Machine Payments Protocol. You resolve it by configuring an MPP agent to automatically negotiate and pay the required fee using a pre-funded wallet, allowing the request to complete.