stripe-link-cli

Completes merchant purchases via Stripe Link using one-time virtual cards or Shared Payment Tokens.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill stripe-link-cli-vivekgoquest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stripe-link-cli
Source: https://github.com/vivekgoquest/hermes-agent-stable/tree/main/optional-skills/payments/stripe-link-cli
Command: npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill stripe-link-cli-vivekgoquest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @stripe/link-cli.

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.

Frequently Asked Questions about stripe-link-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I let an AI agent make purchases with Stripe Link?▼

Install @stripe/link-cli globally, authenticate with link-cli auth login, then create a spend request with link-cli spend-request create and --request-approval. The user approves each spend in the Link mobile or web app before any credential is issued.

How to pay an HTTP 402 merchant API with Stripe?▼

Decode the raw WWW-Authenticate header with link-cli mpp decode to validate the challenge, then create a spend request with --credential-type shared_payment_token and pay via link-cli mpp pay. Merchants without method="stripe" are unsupported.

Does Stripe Link CLI work on Windows or outside the US?▼

No. The upstream link-cli does not support Windows, so this skill is gated to Linux and macOS. It is also US-only because a US-based Link account is required, and auth login will fail elsewhere.

Can the agent approve its own spend requests?▼

No. Every spend request with --request-approval pings the user's Link app and polls until the user approves or denies. The CLI exits non-zero on denial or timeout, and running as an MCP server does not bypass approval.

How are card numbers kept out of agent logs?▼

Retrieve credentials with link-cli spend-request retrieve using --output-file, which writes the card JSON with 0600 permissions. Stdout shows only redacted fields like brand and last4, and the file should be deleted after the purchase.

What are the prerequisites for using Stripe Link CLI?▼

You need Node.js 20+ on PATH and the @stripe/link-cli package installed globally or via npx. The Link account, payment method, and approval app are set up interactively during the first auth login and spend request.