Credits and developer plans
Updated October 26, 2026
What developer accounts pay, the three plans, and how credits are bought, used and topped up.
Who pays what
- An agent working in a member's rooms uses that member's plan. Its uploads count toward the member's space and its reads toward the member's monthly downloads, like the member's own. It never uses credits.
- A developer account (an account for programs, using the S3 endpoint) pays with credits, at the prices below.
Prices
| Price | |
|---|---|
| Storage (what your S3 keys store; never your vault) | $0.012 per GB a month, metered hourly |
| Downloads | $0.02 per GB downloaded. Every GB counts; developer accounts have no free download allowance |
| Requests | Free |
A GB is 1,000,000,000 bytes. Storage is charged for the hours it's kept: 1 GB kept for a whole month costs $0.012; kept for half a month, about $0.006.
Prices are in US dollars. Tax is added on top at checkout where it applies.
Plans
Pay as you go, or a monthly plan that includes a month of usage:
| Plan | Price a month | Usage included each month |
|---|---|---|
| Pay as you go | $0 | None: buy credits when you need them |
| Dev | $5 | $5.00 |
| Build | $25 | $26.50 |
| Scale | $100 | $108.00 |
- A plan's included credits last until the end of the month they were paid for. What's left then expires.
- Usage draws on the month's included credits before bought credits.
- A plan renews each month on the card it was bought with. When a plan ends, the account returns to pay as you go; bought credits stay.
Credits
- Buying: from $5 to $1,000 at a time, on Stripe's checkout.
- Bought credits never expire.
- What uses them: storage, every hour, and downloads as they're made. Requests don't.
- The balance and this month's storage and download spending are shown under Credits on the Rooms page.
Automatic top-ups
Optional. When the credits run out, the card last paid with is charged a set amount (at least $5), as an invoice with tax shown, up to a monthly limit you set. The limit can be anything up to $10,000.
Emails
- 20% left: when the balance falls to 20% of the last top-up or of the plan's monthly credits, whichever is larger, one email says so.
- Run out: if there's nothing left and no top-up can be made (it's off, or the monthly limit is reached), one email says so.
When credits run out
- New uploads pause. The S3 endpoint answers
QuotaExceededuntil there are credits again. - Everything stored stays, and downloads keep working.
- Adding credits, raising the monthly limit, or choosing a plan lets uploads carry on at once.
How billing works, step by step
- On Rooms → Credits, choose a plan or an amount of credits.
- Stripe's checkout takes the card and the billing address; tax is added where it applies.
- When Stripe confirms the payment, the credits appear (a plan's when each month's invoice is paid).
- Every hour, storage since the last hour and any new downloads are taken from the balance.
- When a new month begins, last month's unused included credits expire and the month's counters start again.
Each payment is counted once, however often Stripe repeats its notice.
Usage
The usage page (/agents/usage) shows, by month: for each agent door, the room's stored bytes and the door's reads, bytes read, writes, deletes and shares; for each S3 key, its requests and bytes downloaded; and the credits spent on storage and downloads. There's a CSV export. Totals only, never names. Usage is kept 13 months.
Good to know
- A spending cap per agent door isn't offered: an agent's downloads count toward the member's plan.
- There's no separate sign-up for developer accounts. A developer account is an ordinary Terebyte account that has opened Credits.