Credits, plans and your own API key
Journeys runs your journeys on a real browser and a real AI model. That costs money every time a journey runs, so there is a meter. This page explains it.
One credit is one step
A step is one thing the agent does: it looks at the page, decides, and acts — clicks a button, types into a field, reads a result. A journey that logs in and confirms the dashboard loaded might take eight steps. A journey that walks a whole checkout might take forty.
Every step costs one credit. You can watch them happen while a journey runs.
What is charged, and what is not
| Charged? | |
|---|---|
| A journey that passes | Yes, one credit per step |
| A journey that fails | Yes. The model did the work, and a failure is the product telling you something |
| The setup actions before the first step | No. They are fixed instructions, with no model call |
| A journey that never starts | No. Refused, cancelled while queued, or stopped before its first step |
| A chain of four journeys | Four journeys, charged separately |
A journey has a step budget — the most steps it is allowed before Journeys stops it. Open the journey's Settings section to change the budget for a custom journey; catalog journeys show their fixed budget there. The allowed range and default shown by the editor come from the service.
A journey only starts if your balance is larger than its budget. In the usual case this leaves enough headroom for the whole journey. The balance is not reserved, though: several journeys running at once draw from the same balance. If they exhaust it together, a run can stop between steps. Journeys keeps the evidence already collected and does not turn that stop into a verdict on your site.
This admission rule means the last few credits in an account may be too few for a large journey while still being enough for a small one.
Credits expire twelve months after you get them, and each batch has its own date. Journeys always spends the batch that expires soonest.
What you get
When you sign up you are given a batch of free credits. No card, no subscription. They are yours to spend on any journey.
Pay as you go offers one-off credit packs. Buying a pack also raises how many journeys can run at the same time.
Standard and Scale are monthly subscriptions. They give you a monthly allowance of credits, a monthly run cap, and more journeys running at once. Open Plans and credits for the current pack sizes, limits, prices, and currency; those values can change without changing how the meter works.
Running out of credits does not delete anything. Your journeys, their schedules and their history stay exactly as they are. Journeys emails you, the site page says so instead of showing you a stale result, and everything resumes on its next slot as soon as your balance can fund the journey's step budget again.
Reaching a plan's run cap is different from running out of credits. No journey can start after all runs in the current billing period have been used, even if the account still has credits. Buying a credit pack does not clear that cap. Upgrade the plan to continue now, or wait for the next billing period, when the run count resets. Journeys keeps the journeys, schedules, history, and credits unchanged while the cap is binding.
Bringing your own OpenAI key
This is part of a plan. If you are on Standard or Scale and you already pay OpenAI, you can point Journeys at your own key instead. Open Settings → Your OpenAI key and paste it.
The key is stored encrypted and is never shown again. Replace it when it changes or remove it to return to credits.
On the free tier or on pay-as-you-go credits, the field is not offered. Those tiers are metered in credits and nothing else.
With a key stored:
- Every journey on your account runs on your key.
- No credits are spent. Not fewer — none.
- The model cost and the rate limits are yours, billed by OpenAI directly.
It is a choice, not a top-up. Journeys never decides between your credits and your key: while a key is stored, the key funds everything.
If your plan ends
Your key stays where it is — nothing is deleted — but it stops funding your journeys, and they go back to spending credits from your next journey onward. If you have no credits left, your journeys stop and Journeys tells you.
You can still remove the key, and you can use it again by subscribing again.
Going back to credits
Remove the key. That is the whole answer, and it takes effect on your next journey.
Credits you bought before storing a key are not lost and are not spent while the key is there. They sit in your account and expire on their normal dates. If you want to use them, remove the key first.
If your key stops working
A key can be revoked, rotated, or run out of quota at OpenAI. When that happens every journey stops at its first step, so no result is a verdict on your site.
Journeys says exactly that. Your journeys read Key not working rather than Down, and the site page explains why. Store a working key, or remove the key to go back to credits — either one fixes it.
Questions people ask
Does a slow or heavy page cost more? Not in credits. A step is a step. Behind the scenes a heavy page does cost us more, and the credit price accounts for that on average.
Can I see what a journey cost? Yes. Each run records the credits it spent, on the run's own page.
Do journeys run while I am out of credits? No, and that is deliberate. A status page that shows green because nothing ran is worse than one that admits it stopped.