What problem does it solve?
Agents that need to pay for things on the user's behalf hit a wall: checkout URLs get dumped into chat, raw card numbers risk leaking into logs, and HTTP 402 / Machine Payment Protocol endpoints require a payment credential the agent cannot produce on its own. This Skill turns the Stripe Link CLI into an agent wallet so purchases are capped, user-approved, and auditable.
Core Features & Use Cases
- Spend requests with user approval: Compose a spend request with merchant, amount (in cents, max $500), line items, and a 100+ character context, then poll until the user approves or denies it in the Link app.
- 402 / MPP payments: Decode payment challenges and pay MPP-protected endpoints with one-time-use Shared Payment Tokens.
- Virtual card checkout: Retrieve one-time virtual card credentials written to a permission-locked file (never printed to the conversation) for standard web checkouts or MCP
complete_checkout tools.
- Checkout interception: Automatically route any checkout URL or payment session produced by other tools through Stripe Link instead of surfacing it to the user.
- Use Case: An agent hits a paid API that returns HTTP 402. It creates a $2.00 spend request in test mode, the user approves on their phone, and the agent completes the payment with a Shared Payment Token.
Quick Start
Ask your assistant to pay for the 402-protected endpoint at a given URL using Stripe Link in test mode with a spend limit of five dollars.