mppx

Name: mppx
Availability: InStock
Author: Tempo

Implement the Payment HTTP Authentication Scheme with a TypeScript SDK.

78|152|Updated Jan 29, 2026

Search Tags:#TypeScript #payment integration #MPP #payment handling #402 payment

Ready to run

npx skills add https://github.com/tempoxyz/mpp --skill mppx-tempoxyz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mppx
Source: https://github.com/tempoxyz/mpp/tree/main/public/.well-known/agent-skills/mppx
Command: npx skills add https://github.com/tempoxyz/mpp --skill mppx-tempoxyz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tempo, stripe, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a TypeScript SDK that simplifies the integration of 402 payment handling and the Machine Payments Protocol (MPP) into client and server applications, eliminating the complexity of payment flows.

Core Features & Use Cases

Payment Handling: Streamlines the handling of 402 Payment Required flows with Tempo, Stripe, and other payment methods.
MPP Integration: Enables seamless integration of MPP into applications for secure and efficient payment processing.
Use Case: For a web application, this Skill can be used to add a payment request to a resource endpoint, allowing users to pay for the resource directly within the HTTP request.

Quick Start

Integrate the mppx SDK into your project to handle 402 payment challenges and receipts.

Frequently Asked Questions about mppx

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

FAQPage Schema

What is the 402 Payment Required HTTP status code and when do I need to handle it?▼

The 402 Payment Required status code is used to request payment before granting access to a resource. You need to handle it when integrating pay-per-resource HTTP flows using the Machine Payments Protocol.

How do I handle 402 payment challenges in a TypeScript application?▼

You can handle 402 payment challenges in a TypeScript application by using an SDK that intercepts the 402 response, processes the payment via Tempo or Stripe, and retries the original HTTP request with the payment attached.

Does this payment handling SDK work with both client and server TypeScript applications?▼

Yes, the TypeScript SDK is designed for both client and server applications, enabling seamless integration of 402 payment handling and Machine Payments Protocol flows across your architecture.

Can I use Stripe to process 402 payment required flows with the Machine Payments Protocol?▼

Yes, the SDK supports Stripe alongside Tempo for processing 402 payment required flows, allowing you to handle payments using the Machine Payments Protocol within your existing Stripe setup.

How does the Machine Payments Protocol integrate with HTTP authentication schemes?▼

The Machine Payments Protocol integrates by utilizing the Payment HTTP Authentication Scheme, allowing applications to attach payment data directly to HTTP requests to fulfill 402 Payment Required challenges.

What are the limitations of using the Payment HTTP Authentication Scheme for resource access?▼

The approach requires both client and server to implement the Machine Payments Protocol, meaning standard HTTP clients without SDK integration cannot automatically process the 402 payment required flows.