Get started
Plans and credits
How billing works: a monthly plan with a weekly allowance, optional top-up credits, and what each request costs.
Kyara Intelligence bills through a subscription with a built-in compute budget instead of a pay-per-token invoice. Your plan includes a weekly allowance, every request draws from your credit balance, and usage never turns into a surprise bill.
Plans
Both plans include every model in the catalog. They differ only in the size of the weekly allowance.
| Plan | Price | Weekly allowance | Plan ID in the API |
|---|---|---|---|
| Spark | $15/month | 40,000,000 credits ($4.00), refreshed every Friday | lite |
| Ember | $30/month | 80,000,000 credits ($8.00), refreshed every Friday | premium |
Subscribe or change plans from the pricing page.
Credits
Balances are tracked in credits at a fixed rate: 10,000,000 credits = $1.00. The balance endpoint reports raw credit amounts; divide by 10,000,000 to get dollars.
How your balance works
Every request spends from your weekly allowance first, then your top-up credits.
Weekly allowance
Your allowance resets to your plan's cap every Friday at 06:00 UTC. The reset happens at the same moment for everyone and can take a few minutes to show up. Unused allowance does not roll over. The allowance is also restored to the full cap when your subscription renews and the renewal is paid.
Changing plans mid-week moves your allowance by the difference between the two weekly caps. Moving up adds the difference right away; moving down removes it, which can leave a shortfall if you already spent more than the smaller plan allows.
The allowance can only be spent while your subscription is active. If a payment fails or your subscription ends, it
is paused until the payment goes through or you subscribe again, which restores it in full. While it is paused,
requests keep running on your top-up credits; once those run out, they return 403 no_active_plan.
Top-up credits
Buy one-time credit packs of $5, $10, $25, or $50 under Billing & credits in the dashboard. A pack adds credits worth its price; taxes, where they apply, are added at checkout. Top-up credits have no cap, never expire, and are spent only once your weekly allowance is used up.
Buying a pack takes an active subscription, but using the credits doesn't. If your subscription ends or a payment fails, the credits you already bought keep working until they are spent.
Can my balance go negative?
Your weekly allowance can. A request is billed after it finishes, so its final cost can be more than you had left. Kyara spends the rest of your weekly allowance, then your top-up credits, and records whatever remains as a negative weekly balance.
The shortfall carries into the next Friday reset: the reset adds your weekly allowance and deducts the shortfall. A paid renewal instead restores the full allowance and clears the shortfall. Top-up credits never go negative.
What a request costs
You pay for actual usage at the per-token prices on each model's page in the catalog, quoted per million input and output tokens, with no separate fees. Cached prompt tokens can cost less than the listed input rate; see prompt caching.
Two things happen around every request:
- Before it runs, Kyara estimates its cost from your prompt size and output limit. Requests without
max_tokensormax_completion_tokensare estimated at the default limit of 8,192 output tokens, and limits above the model's maximum output are lowered to that maximum. The estimate is checked against your weekly allowance plus top-up credits (top-up credits alone while the allowance is paused), and a negative weekly balance lowers that total. If the total falls short, the request is rejected with403 insufficient_balance. The estimate is deliberately conservative and only used for this check, so a lower output limit helps when your balance runs low. - After the response finishes, Kyara bills the actual usage: weekly allowance first, then top-up credits.
You are not charged for:
- Failed requests. A request that returns an error costs nothing, including a stream that fails partway through.
- Empty responses. If the model returns no visible text, nothing is charged, even when it spent tokens on reasoning.
Cancelling a request
If you close a streaming request early, generation stops and you are billed for the prompt and the output produced so far. If no visible text had arrived yet, it is free. Closing the connection on a non-streaming request does not stop the generation, and it is billed as if you had waited for it.
Running out
With an active plan, a request your weekly allowance and top-up credits can no longer cover fails with 403 insufficient_balance. You can:
- Wait for the Friday reset. The weekly allowance resets every Friday at 06:00 UTC, never more than seven days away.
- Buy a credit pack from Billing & credits. Packs stack on either plan and never expire.
Without an active plan, the Friday reset doesn't refill your paused allowance, and only top-up credits count. A request
they can't cover fails with 403 insufficient_balance, and once they are used up, every request fails with 403 no_active_plan. Subscribe again, or fix your payment method from Billing & credits, to restore the allowance.
Checking your balance
- Dashboard: the overview shows your weekly allowance, your top-up credits and the next reset, and the ledger lists every charge, purchase and reset.
- API:
GET /v1/balancereturns exact credit amounts, your weekly cap, and the reset schedule.