Stripe AI is a collection of SDKs, tools, an MCP server, and agent skills for building AI products and businesses with Stripe's billing infrastructure. Developers use it to connect Stripe payments and metering to language models and agent frameworks, while the catalogue entries provide Stripe-specific skills, commands, plugins, and agent integrations.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add stripe/ai --skill stripe-paygit clone --depth 1 https://github.com/stripe/aiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/stripe/ai/stripe-pay)<a href="https://agentmods.dev/skills/stripe/ai/stripe-pay"><img src="https://agentmods.dev/badge/skills/stripe/ai/stripe-pay/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/stripe/ai/stripe-pay"><img src="https://agentmods.dev/badge/skills/stripe/ai/stripe-pay.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00058 | $0.00939 |
| Opus 5.5 | $0.00023 | $0.00376 |
| Sonnet 5.5 | $0.00012 | $0.00188 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
stripe-pay scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- stripe-pay — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
stripe pay
Use stripe pay to send money from the authenticated Stripe business to another Stripe business identified by a Stripe Profile handle, for example @recipient.
The stripe pay command is for business-to-business money transfers. Both the sender and the receiving business must have a Stripe Profile. In addition:
- The sender needs a funded financial account.
- The receiver needs an eligible transfer destination linked to their Stripe Profile.
If the user needs details about financial accounts, read Money Management. The command resolves the recipient’s payout configuration, which can route the payout to an attached financial account or linked bank account, and reports the fee and delivery timing before confirmation. Don’t assume that a transfer is free or instant.
Safety Rules
- Don’t send money unless the user explicitly asks you to make the transfer.
- Before running a command that can send money, show the exact
stripe pay ...command you plan to run and get confirmation. - Use
--agentor--jsonfirst so the user can review the transfer details. - Don’t pass
-yor--yesuntil after the user confirms the reviewed transfer. - Don’t guess at the user’s intent. Don’t guess at the username, financial account ID, amount, currency, internal note, memo, or any other detail. Always confirm with the user.
- Don’t print full API keys back to the user.
Choose the workflow
Read the documentation to accomplish your goal. You must read the relevant page before taking action:
| Goal | Documentation |
|---|---|
| Find or verify a recipient when the user doesn’t provide an exact Stripe Profile handle or network ID | Use Stripe Directory with AI agents |
| Review, send, handle approval, resume, or dry-run a transfer | stripe pay CLI reference |
| Create or manage a Stripe Profile, including a recipient’s transfer destination | Stripe Profile |
| Set up or understand an eligible financial account | Money Management |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago Changed 3577d363c350
- 1mo ago First seen · 62 lines · 58 tokens per session scan A 2a085814fdb5
stripe-pay is a skill published in the GitHub repository stripe/ai (1,952 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 939 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-16.
Other skills, from other repositories
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing…
migrating-mastra-to-pydantic-ai
Migrate TypeScript Mastra applications to Python with Pydantic AI and, only when needed, Pydantic AI Harness. Use when source code imports @mastra/ or relies on Mastra agents, tools, workflows, memory, processors, streaming, approvals, skills, or subagents.
migrating-vercel-ai-sdk-and-eve-to-pydantic-ai
Migrate TypeScript Vercel AI SDK or Eve applications to Python with Pydantic AI and, only when needed, Pydantic AI Harness. Use when source code imports ai, @ai-sdk/, or eve, or relies on generateText, streamText, ToolLoopAgent, useChat, Eve agents, tools, skills, subagents, approvals, sessions, channels, schedules…
migrating-pi-to-pydantic-ai
Migrate TypeScript Pi coding-agent applications, extensions, or packages to Python with Pydantic AI and Pydantic AI Harness. Use when source code imports @earendil-works/pi-, calls createAgentSession, registers Pi extensions, or relies on Pi tools, hooks, skills, sessions, compaction, providers, TUI, RPC, or packages.
ax-python-signature
Use when writing Python code with axllm for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes.
ax-python-llm
Use when writing Python code with axllm for using the generated Ax package, factory functions, package docs, examples, and API reference.