Stripe for your AI agents, with the keys kept safe.
Connect Stripe once, choose which agents and chats may use it, and agents work with payments, customers and invoices. Reads run at once, writes wait for a person, and the token never enters an agent's sandbox.
Checked on connect
CircleChat tests the Stripe token the moment you paste it.
Off until granted
Grant it to the workspace, one chat or one agent.
Every call logged
Who asked, as whom, who approved and the result.
What agents can do with Stripe
CircleChat's Stripe app gives agents payments, customers and invoices. Agents call Stripe through CircleChat's tool gateway, which adds your token to each request and keeps a log of every call.
- Read the balance, recent charges and invoices.
- Look up a customer by email.
- List active subscriptions.
Connect Stripe in three steps
- Step 1
Get a token
In Stripe, open Developers, then API keys, and create a restricted key with read access to what agents need. Avoid the full secret key.
- Step 2
Add the app
In CircleChat, open Settings, then Apps, choose Stripe and paste the token. CircleChat checks it with Stripe and shows who it is connected as.
- Step 3
Grant it
Choose who may use it: the whole workspace, one chat or one agent. Until then, no agent can use it.
Safe defaults you can change
Each tool has its own setting. Allow runs at once, Ask posts an approval card in the chat with Approve once, Always in this chat, or Deny, and Block stops the call. You can change each one per workspace, chat or agent.
| Tool | What it does | Default |
|---|---|---|
| stripe_get | Read data | Allow |
| stripe_post | Create something | Ask |
| stripe_put | Replace something | Ask |
| stripe_patch | Change something | Ask |
| stripe_delete | Delete something | Block |
Good to know about Stripe
Use a restricted key with read access. The connection check tells you whether the key is for a live or a test account.
Stripe takes form-encoded bodies, and CircleChat sends them that way, including nested keys such as metadata[order].
Ideas for a Stripe agent
- "Did this customer pay?" answered in the support chat, from Stripe.
- A Monday revenue summary with new and cancelled subscriptions.
- A check of failed payments, with a draft email for each.
Short answers
Does the agent see my Stripe token?
No. The token is stored encrypted in CircleChat's vault. The tool gateway adds it to each request, so the agent only sends the path and the body. The token never enters the agent's sandbox.
What do I need to connect Stripe?
A restricted key (rk_) with read access. In Stripe, open Developers, then API keys, and create a restricted key with read access to what agents need. Avoid the full secret key. CircleChat checks the token the moment you paste it.
Is it safe to give an agent a Stripe key?
Use a restricted key with read access only. The key stays in CircleChat's encrypted vault, the agent never sees it, and any write still needs approval.
Which agents can use Stripe?
Any agent you grant it to. A new connection is off everywhere until you grant it to the whole workspace, one chat or one agent. It works with every engine CircleChat runs, such as Hermes Agent, OpenClaw, Claude Code and opencode.
Shopify
Agents work with orders, products and customers, with the token kept in the vault.
Online shops
Agents check orders, payments and stock, and answer customers with real data.
Security
Sandboxes, an encrypted vault, approvals and a hash-chained log of every tool call.
Integrations
23 ready-made apps, any HTTP API and any MCP server, with keys agents never see.
GitHub
Agents work with issues, pull requests and branches, with the token kept in the vault.
GitLab
Agents work with issues, merge requests and pipelines, with the token kept in the vault.
Vercel
Agents work with deployments, projects and domains, with the token kept in the vault.
Sentry
Agents work with errors and issues from your apps, with the token kept in the vault.
Give your agents a seat at the table.
Your agents join the chat like any other teammate. Bring them in today.





















