Last updated: September 2026
Jev rate limits and context window
Jev takes 64,000 tokens per request, of which 32,000 is the budget for the state plus the longest question. The account limits are 250,000 tokens per second and 1,200 requests per minute. Input is text only. Input tokens cost $0.042 per 1M, output tokens are free, and there is no free tier.
Every figure on this page, including the summary above, is from TypeSafe's models page and API reference, read on 18 September 2026. The last section works out which limit actually binds you.
Token budget per request
Account rate limits
Schema and modality limits
What each primitive returns, and how the criteria are shaped, is in Choice vs Score vs Noul.
Model strings
Pin the version, do not ride the alias
Confidence thresholds are tuned against a specific model. Whenjev-latest moves to a new version, every threshold you calibrated moves with it and nothing in your logs says so. Send jev-1.13.0 and record it with each answer.SDK defaults
The 10 second default timeout is generous against the 70ms to 500ms TypeSafe publishes for end-to-end response time. If Jev sits in a request path a user is waiting on, set it lower and retry once, because a scorer that hangs is worse than a scorer that says it could not score.
Pricing
Source: typesafe.ai and docs.typesafe.ai/models, September 2026. Ways in that skip the waitlist are on the API access page.
Errors
What the limits mean in practice
Two ceilings run at once: 250,000 tokens per second and 1,200 requests per minute. Convert both to a minute and they cross at a single number. 1,200 requests a minute against 15,000,000 tokens a minute is 12,500 input tokens per request. Below that, the request cap binds and the token budget goes unused. Above it, the token cap binds and you never reach 1,200 requests.
The caps are TypeSafe's published figures. The throughput column is our arithmetic on them, not a measurement.
Social content sits at the far left of that table. A post at X's 280-character limit is somewhere around 70 tokens, and a seven-question request over one is about 430 input tokens. At that size you are 29 times under the token ceiling and pinned to the request cap, which works out on the published caps at 1,200 posts a minute, 72,000 an hour, one post per request.
The fix for the request cap is questions, not requests. All the questions in one request are evaluated in the same parallel pass and share one copy of the state, so attaching an eighth question to an existing call costs you its own tokens and nothing else. TypeSafe's fan-out cookbook measured 13 questions in one request at 12.2x cheaper and 10.0x faster than asking them separately, with no change in the answers. If you are near 1,200 requests a minute, look for two calls about the same state that could be one.
The 32k state budget is not your problem on social
32,000 tokens is roughly 150,000 English characters, which is more than 500 posts at X's 280-character limit. The state ceiling bites on long documents, transcripts and PDFs, not on posts and replies. What does bite on social is the opposite: TypeSafe documents that irrelevant context degrades accuracy, so send the post and the platform, not the thread and the account history.What it costs at those volumes
Our arithmetic on TypeSafe's published $0.042 per 1M input tokens, at about 430 input tokens for a short post carrying seven questions. Output tokens are free, so they are not in the arithmetic.
The number worth carrying around: running out of rate limit costs about $1.30 an hour. Cost is not the constraint at social volume. The request cap is, and after that, whether the answers are right. That question is a different page.
// 429 and 529 are the only two worth retrying.
// 401 and 422 are your request, not the service.
const RETRYABLE = new Set([429, 529]);
async function ask(body: unknown, attempt = 0): Promise<Response> {
const res = await fetch('https://api.typesafe.ai/v1/systemone', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.TYPESAFE_API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify(body),
});
if (RETRYABLE.has(res.status) && attempt < 3) {
await new Promise((r) => setTimeout(r, 200 * 2 ** attempt));
return ask(body, attempt + 1);
}
return res;
}Keep exploring
The primitives, the access routes, and what the limits do not cover.
Choice vs Score vs Noul
The three primitives with exact request and response JSON, and the gotchas.
How to get Jev API access
The waitlist, plus Vercel AI Gateway, OpenRouter and Cloudflare.
Can Jev hallucinate?
Schema conformance is guaranteed. The value inside it is not.
Is Jev an LLM?
No. Typed decisions in one parallel pass, and no text generation at all.
Jev vs GPT
Cost and latency per decision against the frontier models.
Will it go viral?
Seven Jev questions over one X draft, free and with no signup.
One request, seven questions
Will it go viral? is the 430-token request from the table above, running live and free with no signup. The OpenTweet API has its own rate limits, per plan, and publishes to X, Bluesky and LinkedIn in one call.