Glossary: State
State is the material under evaluation on TypeSafe Jev (System One): a string, a JSON object, or an array of text. Every question in the request sees the same state. Jev accepts text only — no images, audio, or video. Question IDs are not used in inference; they are for your code. Write the complete judgment in instructions and criteria. Facts belong in state.
This glossary entry is for builders who already heard of Jev / System One and need a citable definition before they dump an entire ticket dump into the payload. jev.pro is an independent unofficial field guide — not affiliated with TypeSafe AI. Confirm the state concept on docs.typesafe.ai. We do not sell or issue API keys.
How it shows up
POST /v1/systemone takes model, state, and questions. Prefer a named object in production so instructions can point at backtick paths such as ticket.messages[0].text. Unused fields still bill as input tokens and, on jev-1.13, TypeSafe says accuracy falls as distractors grow. Filter first.
Allowed shapes: a single string for one passage; an object for named records; an array for a sequence of messages. There is no hidden session. If you need history, put the slice you need in this request. English is the primary training language; other languages are accepted with currently lower accuracy — see language support on this site.
Vendor-published context limits on the models page: 64k tokens for state plus all questions; 32k for state plus the longest question. Confirm there. Output tokens are described as free on the public list price; that is a vendor claim. Pin jev-latest exploration to jev-1.13.0 once you care about calibration week to week.
Choice, Score, and Noul all see this same state. Unused fields are not signals. Schema-safe ≠ factually correct.
Contrast
State vs instructions. Facts belong in state. The judgment belongs in instructions and criteria. Do not hide the question in a field the model is not asked to read.
State vs signal. State is input. Signals are typed answers.
State vs memory. There is no server-side conversation store in the public evaluation API we read. Replay is your POST.
State vs file URLs. Jev will not crawl. Fetch text yourself, then send text.
Common mistakes
- Sending images, audio, or a PDF binary.
- Leaving unused CRM columns in the object “just in case.”
- Pointing instructions at
ticket.foowhen the object uses another name. - Treating state as the same thing as a question ID.
- Assuming a file URL will be fetched.
See also
FAQ
Is state the same as instructions?
No. Facts belong in state. The judgment belongs in instructions and criteria.
What is the context limit?
Vendor-published on the models page: 64k tokens for state plus all questions; 32k for state plus the longest question. Confirm there.
Do all questions share state?
Yes. That is why extra questions are cheap relative to extra HTTP calls.
Can I attach a file URL?
Only if you fetch it and put text in state. Jev will not crawl for you.
Limits
This is a jev.pro working definition. State is a TypeSafe API field. We do not invent search volume. Schema-safe answers are not automatically factually correct. Context numbers are vendor claims — confirm on the models page.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.