Credits and billing
Model use on LibraOS is paid from your account on console.libraos.com, on the Credits & billing page. There are two ways to pay, and they work together:
- Credits, bought as you go. 1 credit = US$0.10 of model use.
- A Token Plan, a subscription that includes a fixed amount of model use each month.
Using your own provider key or a local model is not charged by LibraOS.
What the balance pays for
One credits balance pays for builds, changes and previews in the Console, published apps, and calls with your model API keys. The same key and balance serve the self-hosted Runtime, your own apps and coding agents such as Claude Code, Codex and AgentD workers.
Use is settled every few minutes, so the balance can lag a little behind. While a build runs, part of the balance can be held for it; the page shows how much is available and how much is held. Recent activity and All activity list every entry: grants, top-ups, refunds and model use.
The Model prices section lists every model with its price in credits per million tokens (input, cached input and output) and the cost of a typical answer (2,000 input tokens and 500 output tokens). Name models in API calls as they appear there.
Buy credits
Under Buy credits, pick an amount and choose Buy credits. Checkout is on Stripe, and the credits are added as soon as the payment goes through. Bought credits never expire. New accounts may also receive trial credits once; the page says so when they do.
When credits run out, publishing, the consultant and API calls stop until you top up, and published apps keep answering for 48 hours. How credits work on the page says whether builds and changes also stop on your account.
Settings → Low-balance emails sends an email when your credits will run out within about a day, again when about two hours are left, and when they run out. The warnings on the Credits page show either way.
Token Plan
The Token Plan is a monthly or yearly subscription that pays for model use up to a monthly amount.
- What it covers: the consultant, previews, published apps and calls with your API keys. Builds do not count against it.
- Limits: the plan has 5-hour, weekly and monthly limits. Any 5 hours may use up to 20% of the month's use, and any 7 days up to 50%. Unused use does not roll over.
- Credits stay separate: the plan adds nothing to your credits balance. Credits you buy are kept for use beyond the plan.
- Price: see Credits & billing for the current price. On 2026-11-03 the Console showed US$249 a month, or US$2,490 a year ("2 months free").
When you are subscribed, the Token Plan card shows the plan, the paid period, when it renews, the plan credits left, and a meter for each window. A meter says when its window resets, or that use older than 5 hours or 7 days stops counting, or that its limit is reached and when it frees up.
At a plan limit
The switch Use credits after the plan limit decides what happens when the plan's 5-hour, weekly or monthly limit is reached:
| Switch | Your API keys and the consultant |
|---|---|
| Off | They pause until the plan frees up. Nothing of theirs is charged to your credits. API calls are refused with 429 plan_limit_reached. |
| On | They go on, charged to your credits balance at list prices, as long as you have credits. |
Either way, previews and published apps go on from your credits when the plan is used up, so a live app does not stop.
Subscribe, change and cancel
- Subscribe: choose Subscribe monthly, or Subscribe yearly where it is offered.
- Change plan or cancel: use Manage billing, which opens Stripe for invoices, your card and cancelling the plan. A cancelled plan runs to the end of the paid period.
- A failed payment: if the last payment did not go through, update your card in Manage billing to keep the plan. Until it is paid, the plan's included use is paused and use is charged to your credits.
API keys, AgentD and the plan
One lk_ key from API keys works for every client: the Runtime, your own
code, Claude Code, Codex, and AgentD's Chat and workers when they are pointed
at api.libraos.com. Calls with that key draw on the Token Plan's included
use first and on your credits after it, under the switch above. Without a
plan, they draw on your credits.
A key can be limited to some models and to a number of requests a minute; see LibraOS model API.