mpp-agent

Install mppx globally with npm, create an account, then run `mppx <url>` against the endpoint. The client handles the 402 challenge and credential exchange automatically and prints the merchant's response on success.

Use Stripe Link's link-cli when the challenge advertises method="stripe" or Link is already configured. Otherwise use mppx for one-off paid calls and debugging, or Tempo Wallet when you want persistent spend controls and service discovery.

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.

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.

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

No. This Skill covers the client side of paying 402 challenges only. For server-side MPP, use the middlewares documented at mpp.dev such as mppx/nextjs, mppx/hono, mppx/express, or mppx/elysia.