Skip to main content
Your RuAPI balance is debited on usage: each request costs exactly the tokens the model actually consumed. No subscriptions, no monthly fee — the only extras are one-off discounts when you top up.

​
How charges are calculated

1

You send a request

Your SDK hits our endpoint. We route it to the appropriate provider.
2

The provider runs it

Returns the response plus token counts (input + output).
3

We deduct from your balance

Your balance is reduced by the USD value of the tokens you used. Internal accounting is in USD at 1 USDT / USDC = 1 USD — no conversion to local currencies.
4

We log the call

In the Console → Logs, every request shows the model, input/output tokens, and the exact deduction.
Vendor prices per token can change. Current per-token rates are shown at www.ruapi.ai and update automatically.

​
Cache and the effective price

Many workloads send the same context over and over — a system prompt, a long document, the history inside agent loops (Claude Code and similar tools). Those repeated input tokens hit the cache and cost far less: about 1/10 of the input price on Claude, and even less on DeepSeek. Exact per-model rates are on the pricing page. On agent workloads the cache covers most of the input — often 80–97% of tokens. So the real average input price comes out well below the list rate. That average is what we show next to each model as the “effective price.”
The “effective price” is an estimate for a typical agent workload at ~80% cache hits, not a fixed rate. Your cache share depends on how much repeated context you send. Output tokens aren’t cached and bill at the normal rate. Writing a prefix to the cache costs slightly more than a normal input token, but only once; every read after that is cheap.
For a breakdown on a real working day — how many tokens go to cache and what it does to the bill — see DeepSeek vs Claude: what one day of work actually costs.

​
A log entry for every request

Every call lands in the Console → Logs. Each row shows the model, the input and output token counts, and the USD amount debited. That lets you check at any time where your balance went and spot requests that cost more than expected.

​
Per-key spend limits

When you create an API key, you can set a spend limit in USD — a cap on how much that single key can draw from your overall balance. Useful for:
  • Production / staging / test keys with different limits.
  • Sharing a key with a contractor, capped to a set budget.
  • Protecting against runaway scripts.
See Authentication for details.

​
Refunds and unused balance

Unused balance doesn’t expire: it sits on your account indefinitely. See the Refund Policy for refund rules.

​
How to pay

Payment methods, USDT networks, and top-up discounts are covered separately — see Top-up Guide.