The credit system
A credit is a unit of work. Each specialist run consumes credits in proportion to its token use, tool calls, and external API costs. The owner sees the running total live in the dashboard, can set per-task and monthly caps, and can top up at any time.
In one breath
- Three meters: model tokens, tool calls, pass-through external API costs.
- Per-task, per-day, monthly caps — silent overage is not possible.
- Self-serve wallet, or metered billing for Enterprise tenants.
What costs credits
Three meters tick at once: model tokens (input + output, by tier), tool calls (browser actions, file writes, web fetches), and pass-through external API costs (LLM-priced research, paid scrapers, ad-spend approvals). The credit price for each is published; the dashboard shows the breakdown after every run.
Caps and the budget guard
Owners can set a per-task cap, a per-day cap, and a monthly ceiling. The budget guard halts a specialist before it exceeds its cap and emits a budget_request_card asking whether to extend or stop. No silent overage.
Top-ups and the wallet
Top-ups happen on Stripe Checkout. The wallet balance is visible in the dashboard; auto-top-up is opt-in. Enterprise tenants run on metered billing rather than wallet credits — see the pricing page for the difference.