All integrations
Stripe
Customers, payments, invoices and subscriptions (test or live).
Payments and finance
How an agent reaches it
- MCP
Official MCP server. The agent lists its tools and calls them.
- REST API
Always available. The agent calls the API directly with your credential attached.
- CLI
The `stripe` command, run on one of your computers with the credential mounted.
How you authenticate
- OAuth
- API key
- Copy a secret key from the Stripe dashboard. Prefer a RESTRICTED key scoped to what the agent needs.
- Test keys start with sk_test_ and live keys with sk_live_. Name the credential so the two are impossible to confuse.
How agents reach it
- Base URL
- https://api.stripe.com/v1
- Pagination
- cursor
- Rate limit
- 100 read/sec and 100 write/sec in live mode; 25/sec in test mode.
- MCP server
- https://mcp.stripe.com
- CLI
- stripe
Common endpoints
| list customers | GET /customers?limit=100 |
| search customers | GET /customers/search?query=email:'[email protected]' |
| list charges | GET /charges |
| list subscriptions | GET /subscriptions?status=active |
| list invoices | GET /invoices |
| issue a refund | POST /refunds |
| read balance | GET /balance |
Worth knowing
- Request bodies are application/x-www-form-urlencoded, NOT JSON. Nested fields use bracket syntax: metadata[order_id]=1.
- Amounts are in the smallest currency unit. 10.00 USD is 1000, and getting this wrong charges 100x.
- A test key against live data (or the reverse) 401s rather than warning. Check the key prefix first.
- Set Idempotency-Key on any POST that creates money movement, or a retry double-charges.