Finance & ops
Stripe billing set up per product, from a plain-English description.
Give each live product its own Stripe account and connect its key to OpenHelm. Describe your prices in plain English and OpenHelm checks the key belongs to a real account, then creates the Stripe product, its prices and the webhook. Revenue from that account then feeds the product's numbers, and a product with no revenue source shows "no revenue data" rather than a made-up zero.
What agents do with Stripe. Recurring jobs, checked every run.
An account per product
When a product goes live without verified Stripe, OpenHelm files a task to connect a key scoped to that product. It refuses a connection already verified for another product, so one product's payments never activate a different one.
Prices from a plain-English description
Write something like "£9 a month or £90 a year" and OpenHelm creates the matching product and prices in Stripe, plus the webhook, and records the result against the product.
Revenue in the product's numbers
Read revenue from the product's own Stripe account so its numbers show what that product actually earns rather than a share of a pooled total.
Connect Stripe. A few minutes, once.
Connect Stripe
Add Stripe under Connections in the OpenHelm app and paste a scoped API key, or provision it programmatically with POST /v1/connections.
Describe the job in plain English
Tell OpenHelm what you want done and how often. It drafts a plan with a schedule, the tools it will use, and a clear definition of done.
Approve the plan
No job fires until you have reviewed the plan. Set the autonomy level to control whether writes execute directly or queue for your approval.
It runs, self-checks and reports
Runs execute in isolated cloud sandboxes on schedule. An independent evaluator scores each run against the goal, and results arrive as logs, emails or data-table rows.
Or provision it over the API (see the Connections API docs):
curl https://api.openhelm.ai/v1/connections \
-H "Authorization: Bearer oh_live_..." \
-H "Content-Type: application/json" \
-d '{ "name": "Stripe", "type": "token", "secret": "<your Stripe API key>" }'
# The secret is write-only: stored encrypted, injected only at run time.Questions
Does OpenHelm create the Stripe account itself?
No. Signing up for the account is yours to do, and so, for now, is adding its secret key to the product's own deployment. OpenHelm handles the rest: checking the key, creating the product, prices and webhook, and recording it all against the right product.
How does OpenHelm connect to Stripe?
With a scoped API key: create one in Stripe, paste it into Connections in the OpenHelm app, or provision it programmatically with POST /v1/connections. The key is stored encrypted and injected only at run time inside an isolated sandbox, and you can rotate or delete it whenever you like.
Can the jobs run on a schedule without me?
Yes, that is the point. Jobs run once, on an interval, or on a cron expression. A scheduler fires them, a watchdog times out anything hung, and a separate evaluator checks each run actually advanced the goal. You approve the plan before anything runs for the first time.
Is my Stripe data safe?
Each run executes in an isolated cloud sandbox with scoped, revocable credentials and no middle-layer copy of your data. Every action is logged per run, results come back with evidence, and the agent never fabricates data it could not verify.
More in Finance & ops
Give your product a team that never clocks off.
Start free in the browser, or run it on your Mac with your own Claude Code or Codex plan.