mpp-agent

Automate HTTP 402 challenge payments for per-request API access via MPP clients.

31|3|Updated May 7, 2026
One-click install
npx skills add https://github.com/markwang2658/hermes-windows-native --skill mpp-agent-markwang2658
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mpp-agent
Source: https://github.com/markwang2658/hermes-windows-native/tree/main/hermes-agent/optional-skills/payments/mpp-agent
Command: npx skills add https://github.com/markwang2658/hermes-windows-native --skill mpp-agent-markwang2658

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables paying for per-request API access when servers return HTTP 402 Payment Required by wrapping the Machine Payments Protocol (MPP) clients within Hermes.

Core Features & Use Cases

  • Wraps MPP clients such as link-cli, Tempo Wallet, Privy Agent CLI, AgentCash, and mppx to automate the 402-challenge flow.
  • Supports Linux and macOS for initial setup and tool selection, with clear guidance for Windows users.
  • Provides installation, account setup, and end-to-end payment workflows for per-request API access.

Quick Start

Initiate a per-request payment flow for a 402 challenge using the recommended MPP client.

Frequently Asked Questions about mpp-agent

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

FAQPage Schema
How do I automate HTTP 402 payment challenges for API requests?▼

To automate HTTP 402 payment challenges for API requests, you can use the Machine Payments Protocol (MPP) to handle the wallet-based payment flow. This Skill wraps MPP clients like link-cli and Tempo Wallet to automate the 402-challenge flow for per-request API access.

What is the Machine Payments Protocol and when do I need it?▼

The Machine Payments Protocol (MPP) is a standard for wallet-based payments required when API endpoints return HTTP 402 Payment Required with a www-authenticate header. You need it to manage per-request payments for accessing 402-gated APIs.

How do I set up an MPP client to pay for per-request API access?▼

To set up an MPP client for per-request API access, install the required Node.js prerequisites and complete the wallet or client setup. This provides an end-to-end workflow including installation, account creation, and transaction execution.

Does HTTP 402 payment automation work on Windows or only Linux and macOS?▼

HTTP 402 payment automation supports Linux and macOS for initial setup and tool selection. Windows users receive clear guidance for running the MPP client workflow, ensuring cross-platform compatibility for per-request API access.

Can I use a specific wallet like Tempo Wallet or AgentCash to handle 402 API challenges?▼

Yes, you can use wallets like Tempo Wallet, Privy Agent CLI, or AgentCash to handle 402 API challenges. This Skill wraps these MPP clients to automate the per-request payment flow and access APIs returning HTTP 402.

What are the limitations of using MPP clients for HTTP 402 challenges?▼

A limitation of using MPP clients for HTTP 402 challenges is the strict prerequisite requirement for Node.js and a configured wallet. Additionally, initial automated setup is optimized for Linux and macOS, with Windows requiring separate guidance.