Jev glossary
API & Models429 Too Many Requests
Rate limit
The throughput caps (250,000 tokens per second and 1,200 requests per minute) that return 429 when exceeded.
- Category
- API & Models
- Also known as
- 429 Too Many Requests
- Reading time
- 1 min
- Related terms
- 3
- Directory entries
- 2
- Docs
- docs.typesafe.ai
- Added
- 2026-09-24
Definition
A request over either the token-per-second or the request-per-minute limit returns 429 Too Many Requests. The SDKs retry with backoff by default and honor the retry-after header when one is present.
TypeSafe warns that limits are adjusting dynamically while demand is high and can change without notice; higher limits are available on custom and enterprise plans.
Tagsapilimits
Related terms
Definitions that connect to this one.
API errorThe four documented failure statuses (401, 422, 429, and 529), with retry guidance for the last two.API & ModelsRetry policyThe SDK configuration for retrying failed requests: attempt count, retryable statuses, backoff, and retry-header handling.API & ModelsExponential backoffThe retry strategy the docs recommend for 429 and 529 responses: wait longer after each attempt instead of retrying immediately.API & Models
From the Jev directory
Directory entries that go deeper on this term.
The model card for jev-1.13.0: $42 per billion input tokens with free output, a 64k context, 250k tokens per second, and how to list the models your account can call.
Jev Guides & ArticlesDocs#official#docs#models
Official
The raw HTTP contract behind every SDK: POST a state plus typed noul, choice, and score questions to /v1/systemone, and get one answer per question, with error codes and retry guidance.
Jev Guides & ArticlesDocs#official#docs#api
Official
From the Jev AI model community
Posts from builders shipping with Jev right now.