Credits
Buy credits when the free tier runs out
One credit is 1,000 input tokens — the same unit TypeSafe bills us in, so what you pay tracks what a request actually costs rather than an average we invented.
Starter
$19
one payment · never expires
172,500 credits
150,000 + 22,500 bonus
billing verified with Creem
- input tokens
- 173M
- typical requests
- ~392,045
- per 1,000 credits
- $0.110
- free-tier months
- 1,725
150M input tokens, once. A real project — on our measured fixtures, about 340,000 decisions.
Most bought
$49
one payment · never expires
517,500 credits
450,000 + 67,500 bonus
billing verified with Creem
- input tokens
- 518M
- typical requests
- ~1,176,136
- per 1,000 credits
- $0.095
- free-tier months
- 5,175
450M input tokens, once. A product in production, or a batch you run every night.
Business
$149
one payment · never expires
1,840,000 credits
1,600,000 + 240,000 bonus
billing verified with Creem
- input tokens
- 1.8B
- typical requests
- ~4,181,818
- per 1,000 credits
- $0.081
- free-tier months
- 18,400
1.6B input tokens, once. Gate every tool call and score every passage without counting.
“Typical requests” assumes 440 input tokens, the mean across the eight fixtures on our benchmark page. Longer states buy proportionally fewer — it is a measured figure, not a flattering one.
What credits also unlock
Beyond the balance itself. These ceilings were always ours rather than the API's — TypeSafe allows far more — so holding credits simply stops us withholding them. You are billed per token either way.
| Limit | Free | With credits |
|---|---|---|
| State, characters | 8,000 | 32,000 |
| Questions per request | 10 | 20 |
| Items per /classify batch | 20 | 50 |
| Characters per item | 4,000 | 8,000 |
| Playground calls a minute | 6 | no limit |
The API itself has no per-minute limit at any tier — a key is metered by credits, not by frequency. The playground limit exists to stop a stranger hammering a free endpoint, which is not a description of somebody paying by the token.
How a credit is spent
A credit is not a call. A request costs ceil(input_tokens / 1,000), with a floor of one. On our own measured fixtures a support ticket with three questions runs about 440 input tokens, so it costs a single credit; an 8,000-character state costs eight. Output tokens are free because Jev generates none.
Nothing here renews. Each pack is a single payment that adds credits to your balance and then does nothing else — no plan to cancel, no card kept on file by us, no monthly charge to notice six months later. Buy another when you run out, or do not.
The free grant is spent first. Every account gets 5 credits a month, and those are used before anything you have paid for — the free half is the half that expires, so spending it first is the arithmetic that favours you rather than us. Purchased credits have no expiry and no subscription behind them.
Refunds and what you are buying
Payment is handled by Creem as merchant of record; card details never reach this site. Credits are consumed as you use them, so a refund is only sensible on an unused pack — ask and it is given, within 14 days, minus anything already spent. Failed requests are not charged, because the charge is settled from the token count in a successful response.
What you are not buying is Jev itself. This is our endpoint, our rulesets and our quota on top of TypeSafe's API. If you want the model directly, the waitlist is free and every ruleset here publishes the exact official call it makes.