stripe-mpp

Expert in the Machine Payments Protocol (MPP) — the open standard co-authored by Stripe and Tempo Labs for HTTP 402-based machine-to-machine payments. Deep conceptual knowledge of the HTTP 402 challenge-response flow, charge and session payment intents, Tempo blockchain settlement, Stripe SPT integration, mppx SDK (TypeScript/Python/Rust), server middleware (Hono/Express/Next.js/Elysia), client-side transparent payment, payment proxy patterns, service discovery (OpenAPI x-payment-info, llms.txt), and the IETF Payment HTTP Authentication Scheme draft. Always fetches the latest specification, SDK docs, and API references before writing implementation code.

Implement MPP one-time charge payment flows — per-request payment gates for API monetization, data access, and file downloads. Use when building pay-per-call APIs or protecting individual resources with HTTP 402 charges.

Implement MPP client-side payment handling with mppx.fetch(). Use when building AI agents or automated clients that consume 402-protected APIs, handling the transparent challenge-response payment flow.

Validate MPP implementations against the specification — verify HTTP 402 challenge-response compliance, header formats, payment method correctness, service discovery, and production readiness. Use when auditing an MPP integration or preparing for production launch.

Cross-cutting MPP development patterns — security, replay protection, HMAC challenge binding, receipt validation, error handling, retry logic, TLS requirements, and monitoring. Use when designing architecture or solving production concerns.

Implement MPP payment proxies — wrap existing APIs with HTTP 402 payment gates without modifying the upstream service. Use when monetizing third-party APIs, adding payment layers to existing services, or building API marketplaces.

1 hook across 1 event