Billing & payments

View as Markdown

Billing happens at the organisation level. There is one credit balance per organisation, and every workspace, every API key, and every Sarvam product draws from it.

There is no billing at workspace level and no per-workspace budget or balance. If you need spend to be genuinely separated, you need a separate organisation, not a separate workspace.

How credits work

Credits are a single prepaid balance shown as Credits Left on Settings → Billing.

  • One balance, every product. Model APIs, Voice Agents, Doc Agents, Content Agents and the rest all spend from the same pool — “buy credits once, use them anywhere”.
  • Shared across workspaces. A call from your staging workspace and a call from production reduce the same number.
  • Credits do not expire.

New accounts start with free credits to explore with. See Credits & Rate Limits for the current signup grant and how rate limits work.

Add credits

1

Open billing

Go to Settings → Billing. Check the organisation name in the sidebar switcher first — credits go to whichever organisation you are currently in.

2

Click Add Credits

Enter the amount you want to add. Amounts below the minimum are rejected before checkout.

3

Pay

Complete the payment in the checkout. The balance updates once the payment is confirmed.

Do not close the payment window before it confirms. A payment abandoned at the QR or card step can be captured without the credit grant completing, which means the money is taken and then refunded automatically rather than turning into credits. If your balance has not moved and you were charged, contact support with the payment reference.

Credit balances can take up to a minute to reflect after a large burst of usage, so a balance that looks slightly stale usually just needs a refresh.

Auto-recharge

Auto-recharge tops your balance up automatically so production traffic does not stop when credits run out.

1

Open Set Up Auto-Recharge

On Settings → Billing, use the Auto-Recharge card.

2

Set a threshold and a top-up amount

The threshold is the balance at which a top-up is triggered; the top-up amount is how much is added.

3

Save a payment method

Auto-recharge needs a stored payment method to charge.

Set the threshold high enough to cover your peak spend for a day or two. If it is set close to zero, a traffic spike can drain the balance and start returning 402 errors before the top-up clears.

Payment history

The Payment History tab on Settings → Billing lists your credit purchases. Newly created organisations show an empty state here until the first payment.

If an invoice download is missing for a payment, the most common cause is a special character (including emoji) in the billing address, which the payment provider rejects. Correct the billing address and contact support to have the invoice reissued.

Plans & pricing

Settings → Plans & pricing shows your current plan and per-API rates.

PlanWhat it is
StarterPay as you go from your credit balance, at list rates.
EnterpriseCustom pricing — higher rate limits, custom concurrency and throughput, volume discounts on credits, dedicated support and SLAs.

Use Request enterprise plan on that page to start a conversation about enterprise terms.

Usage

Settings → Usage shows account-wide usage and spend for the organisation. Because usage is attributed to the workspace a call came from, this is where you see which project is spending what.

Running out of credits

When the balance is exhausted, API calls fail with 402. To recover, add credits — the account resumes immediately, with no need to rotate keys or redeploy. See Errors & Troubleshooting for handling 402 and 429 gracefully.

The dashboard shows a low-balance banner before you run out. Treat it as a prompt to enable auto-recharge rather than topping up by hand each time.