Jev glossary
API & Modelsinput_tokens
Input tokens
The tokens billed on every request: state plus questions, including speculative questions your code ignores.
- Category
- API & Models
- Also known as
- input_tokens
- Reading time
- 1 min
- Related terms
- 4
- Directory entries
- 2
- Docs
- docs.typesafe.ai
- Added
- 2026-09-24
Definition
Only input is billed. State and every question count toward the input total, and the response reports input_tokens under usage so cost can be tracked per call.
Because speculative questions cost tokens even when unused, the docs recommend fanning out on questions several branches can reuse rather than on every question a workflow might ever ask.
Tagsapipricing
Related terms
Definitions that connect to this one.
Output tokensThe tokens Jev emits for answers; they are reported in usage and are free of charge.API & ModelsToken pricingJev's published rate: $42 per billion input tokens, with output tokens free.API & ModelsUsageThe response field reporting input and output token counts for a request, used for cost tracking.API & ModelsSpeculative questionA question whose answer only matters on some code paths, asked anyway because questions are cheap and parallel.Patterns
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
Ask everything the system might need in one request, then let code throw away what it does not use. The ticket-triage example sends a category plus four speculative questions in parallel.
Jev Practices & PatternsDocs#official#patterns#batching
Official
From the Jev AI model community
Posts from builders shipping with Jev right now.