skills.rest
icyzh
icyzhCOMMUNITY
Explore all skills by this author →
Website𝕏@icyzhbeGitHub

mpp-agent

Automate HTTP 402 payments via Machine Payments Protocol with wallet integrations.

1|Updated Jul 31, 2026
Search Tags:#automation#api#payments#wallet#mpp#http-402
One-click install
npx skills add https://github.com/icyzh/hermes-web --skill mpp-agent-icyzh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mpp-agent
Source: https://github.com/icyzh/hermes-web/tree/main/optional-skills/payments/mpp-agent
Command: npx skills add https://github.com/icyzh/hermes-web --skill mpp-agent-icyzh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves HTTP 402 Payment Required errors by facilitating automated payments to services using the Machine Payments Protocol, ensuring uninterrupted access to paid API resources.

Core Features & Use Cases

  • Automated 402 Handling: Detects and responds to payment challenges from merchant APIs.
  • Multi-Wallet Support: Integrates with Tempo, Privy, AgentCash, and Stripe Link for flexible payment options.
  • Use Case: When an agent encounters a pay-per-request API, this skill automatically negotiates the payment using the user's preferred wallet, allowing the agent to continue its task without manual intervention.

Quick Start

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

Frequently Asked Questions about mpp-agent

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

FAQPage Schema
How do I handle HTTP 402 Payment Required errors when accessing APIs?▼

To handle HTTP 402 Payment Required errors, use the Machine Payments Protocol to automate payments to merchant APIs. This automatically resolves payment challenges and ensures uninterrupted access to paid API resources during automated tasks.

What is the Machine Payments Protocol for automated API access?▼

The Machine Payments Protocol (MPP) is a system for facilitating automated payments to services returning HTTP 402 Payment Required challenges. It enables agents to negotiate per-request API access fees automatically using a pre-funded wallet, bypassing manual payment steps.

How do I automate API payments using a wallet with Node.js?▼

You automate API payments by running the mppx client in a Node.js 20+ environment to execute terminal commands. You must configure a pre-funded wallet account from supported providers like Tempo, Privy, AgentCash, or Stripe Link to cover the per-request transaction costs.

Does the Machine Payments Protocol work with Stripe Link and Privy wallets?▼

Yes, the Machine Payments Protocol supports multi-wallet integrations including Stripe Link, Privy, Tempo, and AgentCash. This allows you to select your preferred pre-funded wallet provider to execute automated payment transactions for API access.

What are the requirements to set up automated Machine Payments Protocol transactions?▼

Setting up automated Machine Payments Protocol transactions requires a Node.js 20+ environment and a pre-funded wallet account with a supported provider. You use the mppx client via terminal commands to execute the payment transactions required by merchant APIs.

Why do I need a pre-funded wallet to resolve HTTP 402 challenges?▼

You need a pre-funded wallet to resolve HTTP 402 challenges because the Machine Payments Protocol executes real automated payment transactions per API request. The pre-funded balance ensures the wallet can immediately cover the per-request access fees demanded by the merchant service.

Related Skills

Explore More Software Engineering Skills→
zangjeicyzangjeicy

mpp-agent

Automate micro-payments for HTTP 402 API challenges using the Machine Payments Protocol.

Community
Intermediate
SignmanalSignmanal
1

mpp-agent

Automate HTTP 402 payment processing for MPP-compliant APIs.

Community
Intermediate
NITISH-gitbitNITISH-gitbit

mpp-agent

Automate MPP payments for HTTP 402 Payment Required API responses.

Community
Intermediate
RheasilviaRheasilvia

mpp-agent

Automate HTTP 402 API payments via Machine Payments Protocol handshakes.

Community
Intermediate