Agent skill · software engineering · aiskillstore
mppx
TypeScript SDK for the Payment HTTP Authentication Scheme. Handles 402 Payment Required flows with Tempo, Stripe, and other payment methods. Use when integrating payments or mppx into a client or server application.
Why this skill is useful
Provides specific TypeScript methods and patterns for handling payment flows with Tempo and Stripe that the AI wouldn't reliably generate on its own.
What it needs
Requires typescript installed locally. Requires stripe account access. About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
mppx TypeScript SDK for the "Payment" HTTP Authentication Scheme. Full 402 flow: challenge → credential → receipt. What I can accomplish Add 402 payment handling to a client with Fetch.polyfill or Fetch.from. Protect HTTP routes with server-side MPP Challenges and Receipt responses. Accept one-time Tempo stablecoin payments with tempo.charge. Accept metered Tempo stablecoin payments with tempo.session. Accept one-time card payments with stripe.charge. Verify Credentials directly for custom transports or background workflows. Wrap MCP clients and servers so tool calls can require payment. Required inputs Client integrations need a signing account and one or more client payment methods. Server integrations need a recipient, currency, amount, and MPPSECRETKEY. Tempo examples use chain ID 4217 unless a page explicitly covers Moderato testnet. Stripe examples need a configured Stripe account and Shared Payment Token flow. MCP integrations need the MCP client or server object to wrap. Constraints Keep MPPSECRETKEY server-side and out of logs. Never commit private keys or wallet seeds. Treat runtime 402 Challenges as authoritative for current payment terms. Return id and opaque unchanged when responding to a Challenge. Use USDC.e for Tempo bridged USDC examples, not generic USDC. Client Without polyfilling: Server Methods Method Intent Description --- --- --- tempo.charge charge One-time stablecoin payment (TIP-20 token transfer on Tempo) tempo.session session Streaming payments via payment channels on Tempo stripe.charge charge One-time payment via Stripe tempo() returns [tempo.charge, tempo.session] as a tuple using the current v2 Sessions implementation. Use tempo.charge() or tempo.session() individually if you only need one intent. Use tempo.sessionLegacy only for Legacy Sessions v1 compatibility. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/mppx