mpp-agent

Pay HTTP 402 API requests via Machine Payments Protocol clients.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/episvr/USTB-2026-SummerInternship --skill mpp-agent-episvr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mpp-agent
Source: https://github.com/episvr/USTB-2026-SummerInternship/tree/main/hermes-config/optional-skills/payments/mpp-agent
Command: npx skills add https://github.com/episvr/USTB-2026-SummerInternship --skill mpp-agent-episvr

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 APIs become usable on demand. ## Core Features & Use Cases - Client Selection Guidance: Chooses between link-cli (Stripe Link), Tempo Wallet, Privy Agent CLI, AgentCash, and mppx based on the 402 challenge method and the user's funded wallet. - mppx Fast Path: Installs mppx via npm, creates an account, probes the merchant's 402 challenge with curl, and pays the request with automatic challenge/credential handling. - Pitfall Handling: Covers multi-method www-authenticate headers, zero-amount proof challenges, and Stripe-vs-Tempo method mismatches. - Use Case: A merchant API returns HTTP 402 with a www-authenticate: tempo header. The agent installs mppx, creates an account, and runs mppx <url> to pay and retrieve the actual response. ## Quick Start Ask the agent to pay the HTTP 402 challenge on a given URL using mppx and return the merchant's response.

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 HTTP 402 Payment Required API from an agent?▼

Install mppx globally with npm, run mppx account create, then call mppx <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: mppx, Tempo, Privy, or AgentCash?▼

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

Can Stripe Link pay any HTTP 402 challenge?▼

No. Stripe Link only pays challenges advertising method="stripe". If the www-authenticate header lists only Tempo or other methods, use mppx or the matching wallet instead, since Link will reject non-Stripe challenges.

Does mpp-agent work on Windows?▼

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

Why does a 402 endpoint charge zero dollars?▼

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

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

No. This Skill covers the client side of paying 402 challenges. For server-side MPP, use the mpp.dev quickstart with mppx middlewares for Next.js, Hono, Express, or Elysia.