Usage, the meter and spend caps

The per-bot and per-routine spend-cap switches (docs/superpowers/specs/2026-09-15-p5-g-billing-meter-budgets.md §1.1–§1.2) and the "Your spend by bot, this cycle" section (docs/superpowers/specs/2026-09-14-p2-g-follow-ons.md §1.3) are described here from their approved specs; neither has merged into origin/main yet. Everything else on this page is verified directly against the code. Re-verified at close-out.

What this does for you

This page explains how Botseon meters what your bots spend, resets your weekly allowance, and stops a run before it spends more than you allowed.

Before you start

• You're signed in — see Your account and settings.
• You know which plan you're on and what it includes — see Plans and the trial.
• One credit is one euro cent of model usage at the route's published price; every figure on this page is in credits, with its euro value alongside.

Steps

1. Open the account menu and hover Weekly usage for the flyout: your percent used, the day countdown to reset, and — once on-demand spend is on — what you've spent this monthly cycle against its ceiling. <!-- shot: usage-and-the-meter-01-phone.png | The weekly usage flyout, on a phone --> <!-- shot: usage-and-the-meter-01-desktop.png | The weekly usage flyout, on a desktop -->
2. Open Settings → Usage & Billing for the full picture: the same percent as a bar, the reset countdown, and how many credits you've used and have left this week. <!-- shot: usage-and-the-meter-02-phone.png | The Usage tab, on a phone --> <!-- shot: usage-and-the-meter-02-desktop.png | The Usage tab, on a desktop -->
3. Below it, read the per-bot and per-routine breakdown, credits descending, to see what used your allowance; it reads "No usage recorded yet" until your first run. <!-- shot: usage-and-the-meter-03-phone.png | The per-bot and per-routine breakdown, on a phone --> <!-- shot: usage-and-the-meter-03-desktop.png | The per-bot and per-routine breakdown, on a desktop -->
4. Turn on-demand spend on if you want a run to keep going past your weekly allowance. It needs a payment method and a monthly ceiling you set yourself — None, a fixed amount, or No limit — changeable at any time, on a clock of its own that is never the same countdown as your weekly reset. <!-- shot: usage-and-the-meter-04-phone.png | The on-demand switch and ceiling, on a phone --> <!-- shot: usage-and-the-meter-04-desktop.png | The on-demand switch and ceiling, on a desktop -->
5. Watch what a single run costs against its own, always-on ceiling: 200 credits (about €2.00) and 50 steps for a chat run you start yourself, or 10 credits (about €0.10) and 30 steps for an unattended routine, either way within ten minutes — this applies before you set anything on a bot or a routine. No screenshot: this is a limit the run loop enforces, not a screen of its own.
6. Set a lower spend cap on a bot or a routine, once your deployment offers the control, so one run of that bot or that routine can't spend more than you choose — no screenshot yet: this control has not merged into the product.
7. Check "Your spend by bot, this cycle", once your deployment offers it, for a running total by bot rather than by week — no screenshot yet, for the same reason.

A worked example

A member on Pro (2,000 credits a week) partway through a week, read straight off the meter:

Weekly allowance (Pro):         2,000 credits   (≈ €20.00 of model usage)
Used so far this week:            640 credits   (≈ €6.40)
Remaining:                      1,360 credits   (≈ €13.60)
Percent of weekly credits:           32%
Resets in 4 days

The percent is always a whole number and the countdown is always whole days, rounded up — never an hour and never a date — and both are read from one materialised period row, never summed from raw usage records.

What can go wrong

See also

• Plans and the trial
• Your account and settings
• The desktop app
• The phone app