Integrations · Stripe
A Guild agent can query charges, process refunds, manage customers and subscriptions, and retrieve balance and payout data directly in Stripe. Guild stores the Stripe secret key server-side and injects it into every request, so agent code never handles the credential. Credential policies let you limit which operations each agent can call, and every request runs through Guild’s audit trail.
Book a demo
See how teams govern agents that use Stripe.
Talk to sales
Get access to Guild, then connect Stripe to your first agent.
What the Stripe integration exposes
The integration is published asguildai~stripe-openapi and covers customers, payment intents, charges, refunds, invoices, subscriptions, products, prices, payouts, balance, and Checkout Sessions. Tools follow the stripe_openapi_ naming prefix. Read operations use GET tools; write operations use POST and DELETE tools to create, update, cancel, finalize, void, and delete Stripe objects.
How it works
1
Open credentials in Guild
Go to Access & setup > Credentials in your Guild account or organization. Click Connect, then search for and select stripe-openapi.
2
Paste your Stripe key
Enter your Stripe secret key into the API Key field. Guild sends it as a bearer token in the
Authorization header on every request.3
Import tools into your agent
Import
StripeOpenapiTools from @guildai-services/guildai~stripe-openapi and spread it into your agent’s tools object. Use pick() to include only the tools your agent needs.Why Stripe access needs governing
Stripe credentials carry write access to billing objects: they can cancel subscriptions, process refunds, delete customers, and void invoices. Guild stores the secret key server-side and never exposes it to agent code. The credential proxy injects authentication only after all policy checks pass, so agents cannot bypass access rules. With credential policies, you write ALLOW and DENY rules that restrict whichstripe_openapi_ operations each agent or workspace may call. A rule that denies stripe_openapi_delete_* and stripe_openapi_post_* turns any agent into a read-only reporter. You can scope one credential to multiple agents with different rule sets. By contrast, an unscoped allow-all policy, which Guild creates by default, gives every agent the same access as the key itself.
About the Stripe integration
Agents can read and manage core Stripe billing objects including customers, subscriptions, invoices, and products. They can process refunds, query payment intents and charges, and retrieve balance and payout information. Authentication uses a Stripe secret key. The integration isguildai~stripe-openapi.
Authentication
- Type: API key
- Header: Guild sends the key as a bearer token in the
Authorizationheader
Setup
1
Connect Stripe
In Guild, go to Access & setup > Credentials, click Connect, select stripe-openapi, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with thestripe_openapi_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~stripe-openapi:
All 142 tools
All 142 tools
Frequently asked questions
Can I limit an agent to read-only Stripe access?
Can I limit an agent to read-only Stripe access?
Yes. Write a credential policy that denies all
stripe_openapi_post_* and stripe_openapi_delete_* operations. Guild’s credential proxy blocks any matching request before it reaches Stripe, regardless of what the agent asks for. See credential policies for rule syntax.Does Guild support Stripe webhook events?
Does Guild support Stripe webhook events?
No. The catalog entry for
guildai~stripe-openapi lists no webhook events, so the integration does not receive or process inbound Stripe webhooks.Can different agents in the same workspace use different Stripe accounts?
Can different agents in the same workspace use different Stripe accounts?
Yes. Connect a dedicated credential on each installed agent’s detail page. Guild resolves credentials in order: grants and dedicated credentials take priority over workspace and account defaults, so each agent can authenticate with a different Stripe key.
Where does Guild store the Stripe secret key?
Where does Guild store the Stripe secret key?
Guild stores it server-side and injects it into outbound requests through its credential proxy. Agent code never sees the key. See credentials and security architecture for details.
Put a governed agent on Stripe this week
Book a demo
See how teams govern agents that use Stripe.
Talk to sales
Get access to Guild, then connect Stripe to your first agent.