How credits work

Credits pay for Scaffold's agents and nothing else. Here is how a run spends them, and how caps keep the worst case boring.

All plans5 steps · 4 minUpdated Nov 12, 2026

Key takeaways

  • Hosting, the database, sign-in and email are in the plan within its limits. Credits pay only for agent runs.
  • Every run reserves the top of its estimate first, or what its first model call could cost when that is more, then settles what it used and releases the rest.
  • A run stops at the workspace cap, the agent's limit or a zero balance, whichever comes first, and keeps its work.

Know what uses credits

Planner, the QA agent and Triage spend credits by the token, at the rate of the model they run on: Standard, Advanced or Max. Free workspaces run on Standard. Hosting, Postgres, sign-in for your app's users and email don't use credits.

Watch a run spend

When a run starts, Scaffold reserves the top of its estimate, or what its first model call could cost when that is more. As the agent works, the real cost settles against that reservation, and what's left is released. Every step lands in the workspace's credit ledger, which credit.ledger_list reads. The lab below simplifies this and reserves only the top of the estimate.

Try itRun an agent against a real ledger

Agent

Model

Balance461.80credits

  1. GrantMonthly allowance+500.00500.00

Get your allowance

Paid workspaces get 500 credits every month, spent before any others, and what's left of them lapses when the month ends. Each person gets a one-time grant of 50 starter credits that never refills, in their Free workspace once their email is verified, and owns one Free workspace. Owners on Paid can top up with credit packs.

Set a cap

On Paid, owners set a monthly cap for the workspace and a limit for each agent inside it. At 75% of the cap everyone in the workspace gets an inbox item, and from 90% the meter turns red. A run whose starting reservation would pass the cap doesn't start, and one that reaches it stops with its work kept: raise the cap or top up, then ask again.

Estimate a run

Ask an agent shows each model's rate in credits per 1,000 tokens and the run's likely cost before anything starts. Standard costs 0.06 credits per 1,000 tokens, Advanced 1.20 and Max 2.40, and model.list returns the current rates.

Paying for the plan

Free runs static sites. It holds 2 projects, 1 custom domain and 1 GB of files, deploys 15 times in any 24 hours and builds for 120 minutes a month, and its pages show a small Built on Scaffold badge. Paid adds server code and workers, lifts the project, deploy and domain limits, holds 10 GB of files, builds for 1,000 minutes a month and drops the badge. A workspace that moves to Free keeps what it has but adds nothing past those limits.

Upgrades go through Stripe Checkout, and tax is added at checkout. Owners on Paid open the Stripe customer portal from Manage in Stripe in Settings › Billing for invoices, the card and cancelling. Within 14 days of upgrading, Withdraw from contract here in Settings › Billing, then Confirm withdrawal, moves the workspace back to Free and refunds what you paid, less the credits used, which never cost more than one month's price. Each card, person and browser gets one withdrawal. A credit top-up has its own Withdraw from contract here for 14 days, until all its credits are used. If we end the Terms, or you delete your account after we tell you of a change to them and before it takes effect, the Paid plan ends at once and we refund the time left and the unused top-up credits.

Did this guide help?
Next guideAgents, approvals and undo
Still stuck?Write to us with what you tried. Mention this guide and we'll start from there.
Contact support