mpp-agent

Pay HTTP 402 APIs using Machine Payments Protocol clients.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mppx.

What problem does it solve? When an API responds with HTTP 402 Payment Required, most agents can only log the failure. This Skill lets the agent actually pay per-request for API access using Machine Payments Protocol (MPP) clients, so paid merchant endpoints become usable without manual wallet handling. ## Core Features & Use Cases - Multiple MPP clients: Choose between mppx, Tempo Wallet, Privy Agent CLI, AgentCash, or Stripe Link depending on the 402 challenge method and the user's funded wallet. - Challenge inspection: Probe merchant URLs with curl to confirm they speak MPP and decode the www-authenticate header before paying. - Automated payment flow: mppx handles the 402 challenge/credential exchange automatically and prints the merchant's actual response, with receipt verification via verbose mode. - Use Case: A user hits a paid data API that returns HTTP 402 with a Tempo challenge. The agent installs mppx, creates an account, pays the request, and returns the API response with its payment receipt. ## Quick Start Ask the agent to pay for and fetch a URL that returned HTTP 402 Payment Required using mppx.

Frequently Asked Questions about mpp-agent

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

FAQPage Schema
How do I pay an API that returns HTTP 402 Payment Required?▼

Install mppx globally with npm, create an account, then run mppx followed by the URL. The client handles the 402 challenge and credential exchange automatically and prints the merchant's response on success.

Which MPP client should I use for HTTP 402 payments?▼

Use Stripe Link via link-cli when the challenge advertises method="stripe" or Link is already configured. Use mppx for one-off paid calls and debugging, Tempo Wallet for persistent spend controls, Privy for multi-chain wallets, and AgentCash for pre-priced APIs.

Can Stripe Link pay any HTTP 402 challenge?▼

No. Stripe Link only pays challenges that advertise method="stripe" in the www-authenticate header. Challenges offering only Tempo or other methods must be paid with mppx or a matching wallet client.

Does mppx work on Windows?▼

This Skill is gated to Linux and macOS while the broader payments tooling matures on Windows. It also requires Node.js 20 or later available on PATH.

Why does a zero-amount 402 challenge still require a client?▼

Some MPP endpoints charge $0.00 and only want a proof credential rather than real payment. These challenges work without a funded wallet and should not be treated as broken responses.

Can this Skill add HTTP 402 payments to my own API?▼

No. This Skill covers the client side of paying 402 challenges. To add 402 to your own server, use the mppx middlewares for Next.js, Hono, Express, or Elysia described at mpp.dev.