mpp-agent

Automates HTTP 402 API challenge payments using Machine Payments Protocol wallets.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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 handling of HTTP 402 Payment Required challenges.

Core Features & Use Cases

  • Automated Payment Handling: Automatically detects and responds to 402 challenges from MPP-compliant services.
  • Multi-Client Support: Integrates with various wallet providers like Tempo, Privy, and AgentCash to manage payments.
  • Use Case: When an API returns a payment challenge, the agent uses this skill to negotiate the payment and successfully retrieve the requested data without interrupting the user workflow.

Quick Start

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

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?

Automating HTTP 402 Payment Required challenges involves detecting the payment response from MPP-compliant services and negotiating per-request billing through wallet integrations like Tempo, Privy, or AgentCash to successfully retrieve requested data.

What is the Machine Payments Protocol and when do I need it for API requests?

The Machine Payments Protocol (MPP) facilitates automated machine-to-machine payments for premium APIs. You need it when accessing paid services that return HTTP 402 challenges, requiring credential exchange and payment verification to fulfill requests.

Can I use Tempo or Privy wallets to handle per-request API billing?

Yes, you can use Tempo, Privy, or AgentCash wallets to handle per-request API billing. These wallet integrations manage credential exchange and payment verification for MPP-compliant services returning HTTP 402 challenges.

How do I configure an agent to process MPP payments and retrieve data from paid APIs?

Configuring an agent for MPP payments requires setting up a supported wallet client like Tempo or AgentCash. The agent then automatically detects 402 challenges, negotiates the payment, and retrieves the requested data from the premium API.

Are there limitations when using automated wallet payments for HTTP 402 responses?

Automated wallet payments for HTTP 402 responses require the target API to be MPP-compliant. Payment handling is limited to supported wallet providers like Tempo, Privy, and AgentCash for managing credential exchange and verification.