skills.rest
Signmanal
SignmanalCOMMUNITY
Explore all skills by this author →
GitHub

mpp-agent

Automate HTTP 402 payment processing for MPP-compliant APIs.

1|Updated Jun 25, 2026
Search Tags:#mpp#http-402#paid-apis#api-payments#machine-payments#tempo-wallet#stripe-link
One-click install
npx skills add https://github.com/Signmanal/VIGIL --skill mpp-agent-signmanal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mpp-agent
Source: https://github.com/Signmanal/VIGIL/tree/main/optional-skills/payments/mpp-agent
Command: npx skills add https://github.com/Signmanal/VIGIL --skill mpp-agent-signmanal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When an API returns an HTTP 402 Payment Required response, you cannot access its data or functionality without completing the required payment flow. This Skill automates that process using the Machine Payments Protocol (MPP), eliminating the need to manually handle payment challenges and credential exchanges.

Core Features & Use Cases

  • Multi-Client MPP Support: Works with mppx, Tempo Wallet, Privy Agent CLI, AgentCash, and Stripe Link to match your existing wallet and payment setup.
  • Automated 402 Handling: Automatically parses 402 challenge headers, processes payments, and returns the requested API response without manual intervention.
  • Use Case: A security analyst trying to access a paid threat intelligence feed that returns 402 can use this Skill to pay per request and retrieve the data directly in their VIGIL workflow.

Quick Start

Use the mpp-agent skill to pay for access to the paid API endpoint that returned an HTTP 402 error when you tried to fetch data from it.

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 responses when fetching data from paid APIs?▼

HTTP 402 Payment Required responses block data access until the requested payment flow is completed. The mpp-agent Skill automates this process using the Machine Payments Protocol to parse challenges, process payments, and unlock the API data.

What is the Machine Payments Protocol and how does it work for API billing?▼

The Machine Payments Protocol (MPP) is a standard for automating per-request payments to API endpoints. It handles 402 challenge authentication, payment processing, and receipt verification automatically without manual credential management.

Can I use Tempo Wallet or Stripe Link to pay for HTTP 402 API challenges?▼

Yes, HTTP 402 API challenges can be paid using Tempo Wallet or Stripe Link. The Skill supports multiple MPP client implementations including mppx, Tempo Wallet, Privy Agent CLI, AgentCash, and Stripe Link.

How do I access paid threat intelligence feeds that return a 402 error?▼

Paid threat intelligence feeds returning a 402 error can be accessed directly by using the mpp-agent Skill. It processes the per-request payment via MPP and retrieves the feed data automatically within security analyst workflows.

Do I need to manually manage payment credentials for MPP-compliant APIs?▼

No, manual credential management is not needed for MPP-compliant APIs. The Skill automates 402 challenge authentication, payment processing, and receipt verification by integrating directly with supported MPP client wallets.

Related Skills

Explore More Software Engineering Skills→
brittaniebuffiecsubrittaniebuffiecsu
1

mpp-agent

Automates HTTP 402 payment requests using Machine Protocols Protocol (MPP) via Node.js clients like link-cli, Tempo Wallet, and Privy Agent CLI.

Community
Intermediate
dapperdiversdapperdivers
1

threat-intel-aggregator

Aggregate threat intelligence feeds and vulnerability data into daily security briefings.

Community
Advanced
cxnaivecxnaive

mpp-agent

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

Community
Intermediate
LynxLabVNLynxLabVN

mpp-agent

Automate HTTP 402 API payments using the Machine Payments Protocol.

Official
Intermediate