Stripe
Read and manage Stripe customers, payments, subscriptions and products.
Connect it with: API key. Stripe's own documentation: https://docs.stripe.com/keys.
What agents can do
Connect Stripe so the agents working your tasks can reach it. With it connected, they can:
- Look up a customer, their payments, invoices and subscriptions to answer a support question.
- Create products, prices and payment links when building a checkout.
- Read failed payments and disputes to investigate a billing issue.
- Use test-mode keys to build and test a payment flow end to end.
Before you start
- A Stripe account and the Administrator or Developer role to create API keys.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Stripe
Jaah connects to Stripe with an API key, not with a sign-in button.
Connect with an API key
Find each value first:
- Secret or restricted key: Stripe Dashboard > Developers > API keys > Create restricted key: name it Jaah, give Read (or Write) on only the resources agents need, select Create key, then copy it. A test-mode key (rk_test_ or sk_test_) is safest for development.
- Publishable key: Stripe Dashboard > Developers > API keys > Standard keys > Publishable key, from the same mode (live or test) as the secret key.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Stripe card.
- Name the secret and choose who can use it.
- Fill in Secret or restricted key, Publishable key.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to Stripe with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah makes one read-only call to Stripe with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: secret_key, publishable_key.
Tell the agent in your task description which secret to use, for example “use the Stripe secret org/stripe”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Stripe once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Stripe's side too, revoke or delete the key at Stripe.
Limitations
- A restricted key does exactly what its permissions allow; agents get a permission error elsewhere.
- Live and test mode keys reach separate data: a test key never touches real payments.
- Stripe rate-limits API calls (about 100 a second in live mode, 25 in test mode).
- Agents can do only what the connected Stripe account allows.
Troubleshooting
Test says Stripe rejected the key (401)
The key was rolled, deleted or mistyped. Create a new restricted key and select Replace.
Test passes but agents get a permission error
The restricted key lacks that resource. Edit its permissions in Developers > API keys.
Agents cannot find a payment you can see in the Dashboard
The key is from the other mode. Live payments need a live key, test ones a test key.
Still stuck? Select Test and read the result: it names the value Stripe refused and the status it answered.
FAQ
Secret key or restricted key?
A restricted key: it limits agents to what they need, and you can revoke it without affecting your app.
Why the publishable key?
Agents building a checkout need it in client-side code. It is public by design.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Stripe account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.