Stripe

Stripe is the answer to questions for which you would otherwise filter and export in the dashboard. The assistant searches, reads and calculates, across customers, invoices, subscriptions, payouts and disputes.

• “How much revenue did we have last month, and how much of it was refunded?”
• “Which subscriptions were cancelled this week?”
• “Are there open disputes, and what amounts are involved?”
• “Show me all failed payments for this customer.”

1. 01In the Stripe dashboard under Developers open the API keys tab (https://dashboard.stripe.com/apikeys).
2. 02Click Create restricted key.
3. 03Give a name and set Read for exactly the resources the assistant should see. Write stays off.
4. 04Confirm the two-factor prompt, copy the key and keep it safe. It starts with rk_live_ or rk_test_ and is not shown again.

With Stripe there is no sign-in detour, but a restricted API key. There is a factual reason: for connected accounts Stripe does not offer sign-in, and a restricted key can be cut much more precisely anyway.

1. 01In anymize open Apps, then Connectors, search for Stripe and paste the restricted key from the section above.
2. 02If you work as a Connect platform, also enter the account ID of the connected account. Leave empty means: your own account.

The tool set comes from Stripe and besides search and read also includes write operations. That is why the tile says “read and write”. Whether any of that is possible at all you do not decide in chat, but the key does.

The restricted key is the real limit. If you give it only read rights, even the best request cannot change anything, because Stripe rejects it. That is exactly why this step is so explicit in the guide.

Customer names, email addresses, billing addresses, card data and payment references are replaced by placeholders before they go to an AI model. The analysis calculates with amounts and placeholders; you read it with the real customer names.