Pricing
Celeris uses prepaid, per-token billing. Buy credits in the Console; completed requests draw from the workspace's balance according to token usage. There are no subscriptions, seat charges, or minimum commitments.
Rates
| Tier | Prompt tokens | Completion tokens |
|---|---|---|
| General | US$2 per million | US$6 per million |
Estimating costs
Completed responses report exact token counts in their usage block:
"usage": {"prompt_tokens": 27, "completion_tokens": 2, "total_tokens": 29}
Cost per call is prompt_tokens × $2/M + completion_tokens × $6/M. The
following examples show approximate costs for common
agentic workloads:
| Workload | Prompt | Completion | Cost per call | Calls per US$1 |
|---|---|---|---|---|
| Classification / routing | ~30 tokens | ~4 tokens | ~$0.000084 | ~12,000 |
| Judge / rerank scoring | ~120 tokens | ~3 tokens | ~$0.000258 | ~3,900 |
| Structured extraction | ~200 tokens | ~48 tokens | ~$0.000688 | ~1,500 |
| Query rewriting | ~60 tokens | ~24 tokens | ~$0.000264 | ~3,800 |
Two request settings have the greatest effect on spend:
- Set
max_tokensdeliberately. Completion tokens cost three times as much as prompt tokens, and a limit bounds the cost of unexpected output. - Keep prompts concise. Repeated instruction tokens are billed on every call.
What is — and isn't — charged
- Served requests are charged from their exact
usagetoken counts — the same token volumes the usage dashboard aggregates. - Rejected requests are not charged. This includes throttled
(
429), unauthorized (401), and out-of-credit (402) requests. - Server-side failures are free. You are never charged for a
502or503. - A client disconnect does not guarantee cancellation. If processing continues after a disconnect, the request may still be charged for work performed.
Buying credits
Buy credits with a card (Stripe) in the Console, in preset amounts of $10 / $20 / $50 / $100 or a custom amount between $10 and $1,000 per purchase. Receipts are emailed automatically, and invoice documents remain available from Billing.
When your balance reaches zero, API calls return
402 insufficient_quota until you add credit. See
Going to production for production
monitoring guidance.
For reserved capacity, custom limits, or invoicing beyond self-service top-ups, contact us.