What problem does it solve? It lets an AI agent pay for goods and APIs on the user's behalf through Stripe Link, while keeping every spend gated behind an explicit approval in the user's Link app and keeping raw card numbers out of the agent's context. ## Core Features & Use Cases - Approval-gated spend requests: Creates spend requests that ping the Link mobile/web app and block until the user approves or denies — the agent can never self-approve. - Two credential types: Issues one-time-use virtual cards for standard web checkouts, or Shared Payment Tokens (SPT) for merchants returning HTTP 402 with method="stripe". - Secure credential handling: Writes card details to a 0600-permission file via --output-file so the PAN never enters transcripts or logs. - Use Case: A merchant API returns HTTP 402. The agent decodes the challenge with link-cli mpp decode, creates an SPT spend request, waits for the user's in-app approval, and completes the payment with link-cli mpp pay. ## Quick Start Ask the agent to buy an item or pay a merchant API, and it will log in to Link, request your approval in the Link app, and complete the checkout with a one-time virtual card.