Plans and credits

Kyara Intelligence uses a subscription with a built-in compute budget instead of pay-per-token invoicing. Your plan includes a weekly allowance, every request draws from your credit balance, and you can never wake up to a surprise bill.

​

Plans

Both plans include every model in the catalog. The only difference is the size of your weekly allowance.

​

Credits

Balances are tracked in credits at a fixed rate: 10,000,000 credits = $1.00 USD Spark’s weekly allowance holds 40,000,000 credits ($4.00). The balance endpoint reports raw credit amounts. Divide by 10,000,000 to convert credits to dollars.

​

How your balance works

Every request spends from your weekly allowance first, then top-up credits.

​

Weekly allowance

Your plan’s allowance resets to full 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. Your allowance is also restored to the full plan cap when your subscription renews or you change plans. If a payment fails, your allowance is paused until the payment is fixed, after which the full allowance is restored. While it is paused, requests keep working as long as you have top-up credits; once those run out, requests return 403 no_active_plan.

​

Top-up credits

You can buy optional one-time credit packs from the store. Top-up credits have no cap and never expire. Kyara spends them only after your weekly allowance is exhausted. You need an active subscription to buy credit packs, but you do not need one to use them. If your subscription ends or a payment fails, any credits you already bought keep working until they are spent.

​

Can my balance go negative?

Your weekly allowance can go below zero. Kyara settles the actual cost after a response finishes, so a request can complete after using the remaining allowance. The shortfall carries into the next Friday reset. The reset adds your plan’s weekly allowance, then deducts the shortfall. A subscription renewal or plan change instead restores the full allowance and forgives the shortfall. Purchased top-up credits never go negative. They can keep requests running while your weekly balance is below zero.

​

What a request costs

You pay for actual usage at the per-token prices listed in the model catalog, quoted per million input and output tokens, with no separate fees on top. Cached prompt tokens can be billed below the listed input rate. Two things happen around every request:

1. Before the request runs, Kyara estimates its cost from your prompt size and requested output length. Requests that do not set max_tokens or max_completion_tokens are estimated at the default limit of 8,192 output tokens, and explicit limits above the model’s maximum output length are lowered to that maximum. Setting an explicit limit lowers the estimate if your balance is running low. Kyara checks the estimate against your weekly allowance and top-up credits combined. A negative weekly balance reduces the available total. If the total cannot cover the estimate, the request is rejected with a 403 error and the code insufficient_balance. The estimate is deliberately conservative and is used only for this check; billing is based on the usage reported when the response finishes.
2. After the response finishes, Kyara bills the actual usage. It spends the weekly allowance first, then top-up credits.

You are not charged for:

• Failed requests. Any request that returns an error, including a stream that fails partway through, costs nothing.
• Empty responses. If the model returns no assistant content, even when it produced reasoning tokens, nothing is charged.

If you cancel a streaming request before it finishes, generation stops and you are charged for the output produced up to that point. Bigger prompts, longer outputs, and more expensive models consume your budget faster. You do not need to do any token math yourself. The dashboard and the balance endpoint show what you have left and the weekly reset schedule.

​

Running out and topping up

When your weekly allowance and top-up credits are both exhausted, requests fail with 403 insufficient_balance. The next Friday reset is at most seven days away. You have two options:

​

Checking your balance

• Dashboard: the usage page shows your weekly meter, next reset date, top-up balance, and a ledger of your usage and credit purchases.
• API: call GET /v1/balance with your API key to read exact credit amounts, your weekly cap, and the reset schedule.