Stripe

01

Setup

Connect with Stripe

1. 01Start the install. In the superagnt app open Integrations, pick Stripe and click Connect with Stripe.
2. 02Approve the connection. Stripe asks you to connect your account with read and write access.

Paste a secret key

If Connect with Stripe is not offered, the connect dialog opens on the key form. To use a key instead of OAuth, click Use API key instead.

1. 01Get a key. In the Stripe Dashboard open Developers → API keys and copy a secret key (sk_live_..., or sk_test_... for test mode). A restricted key works too: scope it to the resources your agents need.
2. 02Paste it. Paste it as the Secret key on the Stripe connection.

When a workspace has both an OAuth install and a pasted key, calls use the OAuth install.

02

Things to know

• Amounts are integers in the currency's smallest unit, such as cents for USD.
• Lists take limit (up to 100). Customers, charges and payment intents also page with starting_after, the id of the last object you received.
• A Stripe-Version header on a REST call is not forwarded to Stripe.
• Over REST, a Stripe path outside the operations list is still forwarded, without validation.
• Deleting a customer and cancelling a payment intent or a subscription cannot be undone, and always ask a person first by default. Creating and updating customers, and creating setup intents, Checkout sessions, products and prices, run without asking.

03

Examples

List recent payment intents

curl "https://api.superagnt.com/v1/connections/stripe/payment_intents?limit=5" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY"

Create a customer

curl -X POST "https://api.superagnt.com/v1/connections/stripe/customers" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d '{"email":"jenny.rosen@example.com","name":"Jenny Rosen","metadata":{"crm_id":"6735"}}'

Create a Checkout session

curl -X POST "https://api.superagnt.com/v1/connections/stripe/checkout/sessions" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d '{
    "mode": "subscription",
    "success_url": "https://example.com/success",
    "cancel_url": "https://example.com/cancel",
    "line_items": [{"price": "price_1Example", "quantity": 1}]
  }'

Stripe receives line_items[0][price]=price_1Example&line_items[0][quantity]=1. In the response, data.url is the hosted Checkout page.

04

Receiving Stripe webhooks

This connection calls Stripe; it does not receive Stripe's events. To trigger an agent from Stripe, create an inbound endpoint in the superagnt app (Webhooks, the Inbound tab, Create Webhook), copy its URL, https://api.superagnt.com/webhooks/ingest/<hookId>, and add it as a webhook endpoint in Stripe with the events you want. Stripe signs deliveries with its own Stripe-Signature header, which an inbound endpoint does not check, so leave the endpoint's signature verification off and keep its URL secret. Binding the endpoint to an agent or a pipeline is on Receiving webhooks.

21 tools, one per resource and risk

MCP servers and agents on the grouped surface list Stripe as these tools. Each takes an action, and the ones that work across record types an object. Every operation also keeps its own per-operation name, in the next table, which works on every server. How grouping works: Grouped tools.

All 30 operations

Each operation is a REST path under https://api.superagnt.com/v1/connections/stripe and an MCP tool. The per-operation tool name is the one permissions, approvals and usage records use.

Related