Jev 1.13 is TypeSafe’s versioned System One model for structured decisions. Its producer identifier is jev-1.13.0. It evaluates text or textual JSON state against typed questions and returns values and probability distributions directly, without composing a written answer. The edition suits classification, routing, condition checks and rubric judgments whose possible outcomes are known before the request.
Supply a string, a JSON object or an array of text values as the state. Use named fields when the evidence contains related records, a conversation and a policy. Retain the parts each question needs and refer to a specific field or item when that identifies the evidence clearly. Jev 1.13 is text only; images, audio, video and binaries need preparation into text or structured textual fields outside this model.
Each question has a type, instructions and any criteria its type requires. Instructions and criterion descriptions can use text or JSON structure. The producer returns answers under the question identifiers, but those identifiers are not part of inference. Write the complete question rather than relying on an identifier such as urgent to imply the intended criterion. A useful support state can contain the message and impact details while separate questions define its category and severity.
Choice selects the highest-probability option from the unordered set defined by the caller. Its criteria map contains the option keys and descriptions, with null allowed when an option needs no extra explanation. The documented limit is 255 options per Choice. Add an other or no-match option when a taxonomy does not cover all possible evidence, and explain boundaries that a short category name does not settle.
The answer contains the selected option, a probability for every option and confidence. Keep the distribution when two candidates are close instead of treating the selected label as certainty. The selected category can identify a proposed route; the surrounding application decides whether and how to perform that route.
Score uses an ordered array of described levels, with at least two recommended and up to ten supported. Indices start at 0. The numerical result is the probability-weighted average of the level indices, so it may fall between levels. The answer’s legend relates the indices to their descriptions, and the level probabilities show how the judgment is distributed.
For severity, describe the difference between cosmetic impact, a usable workaround and a blocked task. A fractional score can help prioritize or aggregate judgments, while selecting the most probable category is a different operation. TypeSafe’s edition-specific guide warns that Score is weak for reconstructing an exact physical or numerical quantity by interpolating between levels. Keep precise arithmetic and measurements outside the model.
Noul returns the probability, from 0 to 1, that a defined condition is true. Optional true and false criteria clarify the boundary. It has no separate confidence field. A probability near 0.5 indicates uncertainty about yes versus no, not a middle value on a graded scale.
Choice and Score confidence are derived from their own distributions. For Choice with at least two options (n > 1) and selected probability p_max, the documented formula is (p_max − 1/n) / (1 − 1/n): it compares the top outcome with an even split. Score confidence also accounts for the probability-weighted distance from the most likely level, normalized against the spread of a uniform distribution and floored at 0. Thus adjacent ambiguous levels and opposite-end ambiguity have different meanings. Keep the full distribution when the task needs more detail than a single statistic.
Questions in one request see the same state and are evaluated independently. A result from one question is not hidden context for another. Split a broad judgment into focused concerns, then interpret or combine the returned values according to the task. An issue can have a category, an impact rating and a relevance check without turning those independent criteria into one vague priority label.
If a later question needs evidence fetched or options chosen from an earlier result, make that dependency explicit in a later request. For candidate extraction, first obtain the available values from the source, then use a bounded Choice to select among them. Jev 1.13 is not trained for free-form text generation and should not be described as producing an arbitrary new string or a narrative explanation.
The maker lists a 64k-token budget for the state plus all questions combined, and a 32k-token budget for the state plus the longest single question. Both constraints matter. A state that fits the total budget can still leave too little room for an individual question’s instructions and options. Remove unrelated material while keeping the evidence that determines the answer.
English is the edition’s primary training language and the producer reports its best accuracy there. Other languages, including CJK scripts, are accepted but do not have equal accuracy. Use representative source material from the intended language when assessing how probabilities or category boundaries should be interpreted. A text-only input contract does not establish universal multilingual performance.
TypeSafe documents literal reading of scoping words and negations, unreliable counting and arithmetic, difficulty comparing dates as ordered quantities, and reduced reliability with multiple layers of indirection. It recommends doing exact computation in code and giving the model the semantic judgment. Numerical encodings can be less effective than meaningful names, and a large state filled with unrelated detail can distract from the relevant evidence.
The same guide says adversarial content in state can steer the answer; contradictory instructions and criteria can confuse it; and Choice option order can sometimes bias a result toward an early option. Define the actual condition, align instructions with criteria, reduce unnecessary hops, and compare borderline judgments against the source. Keep the Jev 1.13 limits in mind when interpreting its judgments.
A useful Jev 1.13 artifact preserves the state identifier, complete question, options or levels, typed result, probabilities and relevant confidence statistic. Keep the version explicit when results or thresholds depend on this edition. Review uncertain cases against the evidence and let the application perform exact calculations and workflow actions; the model supplies a focused judgment with numerical uncertainty.
", "aboutText": "Jev 1.13 is TypeSafe’s versioned System One model for structured decisions. Its producer identifier is jev-1.13.0. It evaluates text or textual JSON state against typed questions and returns values and probability distributions directly, without composing a written answer. The edition suits classification, routing, condition checks and rubric judgments whose possible outcomes are known before the request.\n\n### State and focused question preparation\n\nSupply a string, a JSON object or an array of text values as the state. Use named fields when the evidence contains related records, a conversation and a policy. Retain the parts each question needs and refer to a specific field or item when that identifies the evidence clearly. Jev 1.13 is text only; images, audio, video and binaries need preparation into text or structured textual fields outside this model.\n\nEach question has a type, instructions and any criteria its type requires. Instructions and criterion descriptions can use text or JSON structure. The producer returns answers under the question identifiers, but those identifiers are not part of inference. Write the complete question rather than relying on an identifier such as urgent to imply the intended criterion. A useful support state can contain the message and impact details while separate questions define its category and severity.\n\n### Choice: a supplied category and its distribution\n\nChoice selects the highest-probability option from the unordered set defined by the caller. Its criteria map contains the option keys and descriptions, with null allowed when an option needs no extra explanation. The documented limit is 255 options per Choice. Add an other or no-match option when a taxonomy does not cover all possible evidence, and explain boundaries that a short category name does not settle.\n\nThe answer contains the selected option, a probability for every option and confidence. Keep the distribution when two candidates are close instead of treating the selected label as certainty. The selected category can identify a proposed route; the surrounding application decides whether and how to perform that route.\n\n### Score: an expected level, not an exact measurement\n\nScore uses an ordered array of described levels, with at least two recommended and up to ten supported. Indices start at 0. The numerical result is the probability-weighted average of the level indices, so it may fall between levels. The answer’s legend relates the indices to their descriptions, and the level probabilities show how the judgment is distributed.\n\nFor severity, describe the difference between cosmetic impact, a usable workaround and a blocked task. A fractional score can help prioritize or aggregate judgments, while selecting the most probable category is a different operation. TypeSafe’s edition-specific guide warns that Score is weak for reconstructing an exact physical or numerical quantity by interpolating between levels. Keep precise arithmetic and measurements outside the model.\n\n### Noul and confidence have distinct meanings\n\nNoul returns the probability, from 0 to 1, that a defined condition is true. Optional true and false criteria clarify the boundary. It has no separate confidence field. A probability near 0.5 indicates uncertainty about yes versus no, not a middle value on a graded scale.\n\nChoice and Score confidence are derived from their own distributions. For Choice with at least two options (n > 1) and selected probability p_max, the documented formula is (p_max − 1/n) / (1 − 1/n): it compares the top outcome with an even split. Score confidence also accounts for the probability-weighted distance from the most likely level, normalized against the spread of a uniform distribution and floored at 0. Thus adjacent ambiguous levels and opposite-end ambiguity have different meanings. Keep the full distribution when the task needs more detail than a single statistic.\n\n### Independent judgments over shared evidence\n\nQuestions in one request see the same state and are evaluated independently. A result from one question is not hidden context for another. Split a broad judgment into focused concerns, then interpret or combine the returned values according to the task. An issue can have a category, an impact rating and a relevance check without turning those independent criteria into one vague priority label.\n\nIf a later question needs evidence fetched or options chosen from an earlier result, make that dependency explicit in a later request. For candidate extraction, first obtain the available values from the source, then use a bounded Choice to select among them. Jev 1.13 is not trained for free-form text generation and should not be described as producing an arbitrary new string or a narrative explanation.\n\n### Edition-specific context and language limits\n\nThe maker lists a 64k-token budget for the state plus all questions combined, and a 32k-token budget for the state plus the longest single question. Both constraints matter. A state that fits the total budget can still leave too little room for an individual question’s instructions and options. Remove unrelated material while keeping the evidence that determines the answer.\n\nEnglish is the edition’s primary training language and the producer reports its best accuracy there. Other languages, including CJK scripts, are accepted but do not have equal accuracy. Use representative source material from the intended language when assessing how probabilities or category boundaries should be interpreted. A text-only input contract does not establish universal multilingual performance.\n\n### Published substantive limitations\n\nTypeSafe documents literal reading of scoping words and negations, unreliable counting and arithmetic, difficulty comparing dates as ordered quantities, and reduced reliability with multiple layers of indirection. It recommends doing exact computation in code and giving the model the semantic judgment. Numerical encodings can be less effective than meaningful names, and a large state filled with unrelated detail can distract from the relevant evidence.\n\nThe same guide says adversarial content in state can steer the answer; contradictory instructions and criteria can confuse it; and Choice option order can sometimes bias a result toward an early option. Define the actual condition, align instructions with criteria, reduce unnecessary hops, and compare borderline judgments against the source. Keep the Jev 1.13 limits in mind when interpreting its judgments.\n\nA useful Jev 1.13 artifact preserves the state identifier, complete question, options or levels, typed result, probabilities and relevant confidence statistic. Keep the version explicit when results or thresholds depend on this edition. Review uncertain cases against the evidence and let the application perform exact calculations and workflow actions; the model supplies a focused judgment with numerical uncertainty.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "d04358bb83b33522dfdaebc5edb2c683ac4c617e913ebd9dd646c262f5f9ae7a", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "typesafe/jev-1.13Jev 1.13 is TypeSafe’s text-only System One decision model. It returns typed Choices, fractional rubric Scores and yes/no probabilities directly, with distributions and model-specific confidence statistics, for classification, routing and focused judgments.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Jev 1.13 is TypeSafe’s versioned System One model for structured decisions. Its producer identifier is jev-1.13.0. It evaluates text or textual JSON state against typed questions and returns values and probability distributions directly, without composing a written answer. The edition suits classification, routing, condition checks and rubric judgments whose possible outcomes are known before the request.
Supply a string, a JSON object or an array of text values as the state. Use named fields when the evidence contains related records, a conversation and a policy. Retain the parts each question needs and refer to a specific field or item when that identifies the evidence clearly. Jev 1.13 is text only; images, audio, video and binaries need preparation into text or structured textual fields outside this model.
Each question has a type, instructions and any criteria its type requires. Instructions and criterion descriptions can use text or JSON structure. The producer returns answers under the question identifiers, but those identifiers are not part of inference. Write the complete question rather than relying on an identifier such as urgent to imply the intended criterion. A useful support state can contain the message and impact details while separate questions define its category and severity.
Choice selects the highest-probability option from the unordered set defined by the caller. Its criteria map contains the option keys and descriptions, with null allowed when an option needs no extra explanation. The documented limit is 255 options per Choice. Add an other or no-match option when a taxonomy does not cover all possible evidence, and explain boundaries that a short category name does not settle.
The answer contains the selected option, a probability for every option and confidence. Keep the distribution when two candidates are close instead of treating the selected label as certainty. The selected category can identify a proposed route; the surrounding application decides whether and how to perform that route.
Score uses an ordered array of described levels, with at least two recommended and up to ten supported. Indices start at 0. The numerical result is the probability-weighted average of the level indices, so it may fall between levels. The answer’s legend relates the indices to their descriptions, and the level probabilities show how the judgment is distributed.
For severity, describe the difference between cosmetic impact, a usable workaround and a blocked task. A fractional score can help prioritize or aggregate judgments, while selecting the most probable category is a different operation. TypeSafe’s edition-specific guide warns that Score is weak for reconstructing an exact physical or numerical quantity by interpolating between levels. Keep precise arithmetic and measurements outside the model.
Noul returns the probability, from 0 to 1, that a defined condition is true. Optional true and false criteria clarify the boundary. It has no separate confidence field. A probability near 0.5 indicates uncertainty about yes versus no, not a middle value on a graded scale.
Choice and Score confidence are derived from their own distributions. For Choice with at least two options (n > 1) and selected probability p_max, the documented formula is (p_max − 1/n) / (1 − 1/n): it compares the top outcome with an even split. Score confidence also accounts for the probability-weighted distance from the most likely level, normalized against the spread of a uniform distribution and floored at 0. Thus adjacent ambiguous levels and opposite-end ambiguity have different meanings. Keep the full distribution when the task needs more detail than a single statistic.
Questions in one request see the same state and are evaluated independently. A result from one question is not hidden context for another. Split a broad judgment into focused concerns, then interpret or combine the returned values according to the task. An issue can have a category, an impact rating and a relevance check without turning those independent criteria into one vague priority label.
If a later question needs evidence fetched or options chosen from an earlier result, make that dependency explicit in a later request. For candidate extraction, first obtain the available values from the source, then use a bounded Choice to select among them. Jev 1.13 is not trained for free-form text generation and should not be described as producing an arbitrary new string or a narrative explanation.
The maker lists a 64k-token budget for the state plus all questions combined, and a 32k-token budget for the state plus the longest single question. Both constraints matter. A state that fits the total budget can still leave too little room for an individual question’s instructions and options. Remove unrelated material while keeping the evidence that determines the answer.
English is the edition’s primary training language and the producer reports its best accuracy there. Other languages, including CJK scripts, are accepted but do not have equal accuracy. Use representative source material from the intended language when assessing how probabilities or category boundaries should be interpreted. A text-only input contract does not establish universal multilingual performance.
TypeSafe documents literal reading of scoping words and negations, unreliable counting and arithmetic, difficulty comparing dates as ordered quantities, and reduced reliability with multiple layers of indirection. It recommends doing exact computation in code and giving the model the semantic judgment. Numerical encodings can be less effective than meaningful names, and a large state filled with unrelated detail can distract from the relevant evidence.
The same guide says adversarial content in state can steer the answer; contradictory instructions and criteria can confuse it; and Choice option order can sometimes bias a result toward an early option. Define the actual condition, align instructions with criteria, reduce unnecessary hops, and compare borderline judgments against the source. Keep the Jev 1.13 limits in mind when interpreting its judgments.
A useful Jev 1.13 artifact preserves the state identifier, complete question, options or levels, typed result, probabilities and relevant confidence statistic. Keep the version explicit when results or thresholds depend on this edition. Review uncertain cases against the evidence and let the application perform exact calculations and workflow actions; the model supplies a focused judgment with numerical uncertainty.
POST /v1/systemonetextdecisions| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits typesafe/jev-1.13 | Default— |
Fieldprovider | Typeschema | RequirementOptional | Values & limits | Default— |
Fieldquestions | Typeobject | RequirementRequired | Values & limits | Default— |
Fieldsession_id | Typestring | RequirementOptional | Values & limits | Default— |
Fieldstate | Typeschema | RequirementRequired | Values & limits | Default— |
Fieldtrace | Typeschema | RequirementOptional | Values & limits | Default— |
Fielduser | Typestring | RequirementOptional | Values & limits | Default— |
Fieldquestions.<id>.type | Typestring | RequirementRequired | Values & limits noul, choice, score | Default— |
Fieldquestions.<id>.instructions | Typestring|object|array | RequirementRequired | Values & limits | Default— |
Fieldquestions.<id>.criteria | Typeobject|array | RequirementOptional | Values & limits Conditions: choice/score: required; noul: optional. choice criteria is object; score is array with minItems1. | Default— |
Fieldquestions.<id>.criteria.true | Typestring|object|array | RequirementRequired | Values & limits Applies when: noul criteria object supplied | Default— |
Fieldquestions.<id>.criteria.false | Typestring|object|array | RequirementRequired | Values & limits Applies when: noul criteria object supplied | Default— |
noul · Required: state, questions.<id>.type=noul, questions.<id>.instructions
choice · Required: state, questions.<id>.type=choice, questions.<id>.instructions, criteria object
score · Required: state, questions.<id>.type=score, questions.<id>.instructions, criteria array with minItems1
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, state, questions |
Parametermaterial_types | Contracttext |
Parameteroptional_controls | Contractprovider, session_id, trace, user |
Parametermultimodal_input_binding | Contractnull |
Lifecycle: synchronous
Send the exact model ID and retain the complete native response.
Tariff references do not add request options. Supported parameters are listed for the selected method.
Match each charge to the conditions shown. Use one rate for each set of alternative configurations.
| Configuration | Rate schedule | Context tokens, more than | Context tokens, up to and including | Charge |
|---|---|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Context tokens, more than— | Context tokens, up to and includingNo upper bound | Charge Input · Input tokens $0.000084 / 1K tokens Output · Output tokens $0 / 1K tokens Input · Cache read — / 1K tokens Input · Cache write — / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
| ConfigurationRequest-length tier 1 | Rate schedule— | Context tokens, more than0 | Context tokens, up to and includingNo upper bound | Charge Input · Input tokens $0.000084 / 1K tokens Output · Output tokens $0 / 1K tokens Input · Cache read — / 1K tokens Input · Cache write — / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
{\n "model": "typesafe/jev-1.13",\n "questions": {\n "is_bug": {\n "criteria": {\n "false": "The customer is asking a question or requesting a feature.",\n "true": "The customer describes broken or unexpected product behavior."\n },\n "instructions": "Is the customer reporting a software defect?",\n "type": "noul"\n },\n "team": {\n "criteria": {\n "account": "Login, permissions, or profile issues.",\n "frontend": "Rendering, layout, or browser compatibility issues.",\n "payments": "Checkout, billing, or payment processing issues."\n },\n "instructions": "Which team should own this ticket?",\n "type": "choice"\n },\n "urgency": {\n "criteria": [\n "Can wait for the next release",\n "Should be fixed this week",\n "Blocking revenue right now"\n ],\n "instructions": "How urgent is this ticket?",\n "type": "score"\n }\n },\n "state": {\n "customer_tier": "enterprise",\n "ticket": "My checkout page shows a blank screen after I click Pay. I have tried two browsers."\n }\n}set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\n: "${AILOOT_REQUEST_FILE:?Set your actual JSON request file}"\nexport AILOOT_REQUEST_FILE\npython3 - <<'PY_REQUEST'\nimport json,os\nfrom pathlib import Path\np=json.loads(Path(os.environ['AILOOT_REQUEST_FILE']).read_text(encoding='utf-8'))\nif not isinstance(p,dict): raise SystemExit('Request must be a JSON object')\np['model']='typesafe/jev-1.13'\nPath('request.json').write_text(json.dumps(p,ensure_ascii=False),encoding='utf-8')\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/systemone \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o result.json\npython3 - <<'PY_RESULT'\nimport json\nfrom pathlib import Path\nprint(json.dumps(json.loads(Path('result.json').read_text()),ensure_ascii=False,indent=2))\nPY_RESULT\njson
Keep every complete returned response, file and content part.
Every supplied question-ID answer with its exact type, noul/choice/score value, confidence, probabilities and legend is retained. Entire original JSON is stored and returned only after settlement.
Preserve original operation and full/partial reply; do not replay POST.
| Field | Type |
|---|---|
Fieldmodel | Typestring |
Fieldid | Typestring |
Fieldprovider | Typestring |
Fieldanswers.<id>.type | Typestring |
Fieldanswers.<id>.noul | Typenumber |
Fieldanswers.<id>.choice | Typestring |
Fieldanswers.<id>.score | Typenumber |
Fieldanswers.<id>.confidence | Typenumber |
Fieldanswers.<id>.probabilities | Typeobject |
Fieldanswers.<id>.legend | Typeobject |
Fieldusage.input_tokens | Typeinteger |
Fieldusage.output_tokens | Typeinteger |
Fieldusage.cost | Typenumber |
| Response | Condition | Next step |
|---|---|---|
Response400 · invalid_request_error | ConditionInvalid required field, representation or value | Next stepCorrect the indicated request field. |
Ailoot Ultra typesafe/jev-1.13, ~typesafe/jev-latest
Use the method paths shown above.
~typesafe/jev-latestJev 1.13 is TypeSafe’s text-only System One decision model. It returns typed Choices, fractional rubric Scores and yes/no probabilities directly, with distributions and model-specific confidence statistics, for classification, routing and focused judgments.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Jev 1.13 is TypeSafe’s versioned System One model for structured decisions. Its producer identifier is jev-1.13.0. It evaluates text or textual JSON state against typed questions and returns values and probability distributions directly, without composing a written answer. The edition suits classification, routing, condition checks and rubric judgments whose possible outcomes are known before the request.
Supply a string, a JSON object or an array of text values as the state. Use named fields when the evidence contains related records, a conversation and a policy. Retain the parts each question needs and refer to a specific field or item when that identifies the evidence clearly. Jev 1.13 is text only; images, audio, video and binaries need preparation into text or structured textual fields outside this model.
Each question has a type, instructions and any criteria its type requires. Instructions and criterion descriptions can use text or JSON structure. The producer returns answers under the question identifiers, but those identifiers are not part of inference. Write the complete question rather than relying on an identifier such as urgent to imply the intended criterion. A useful support state can contain the message and impact details while separate questions define its category and severity.
Choice selects the highest-probability option from the unordered set defined by the caller. Its criteria map contains the option keys and descriptions, with null allowed when an option needs no extra explanation. The documented limit is 255 options per Choice. Add an other or no-match option when a taxonomy does not cover all possible evidence, and explain boundaries that a short category name does not settle.
The answer contains the selected option, a probability for every option and confidence. Keep the distribution when two candidates are close instead of treating the selected label as certainty. The selected category can identify a proposed route; the surrounding application decides whether and how to perform that route.
Score uses an ordered array of described levels, with at least two recommended and up to ten supported. Indices start at 0. The numerical result is the probability-weighted average of the level indices, so it may fall between levels. The answer’s legend relates the indices to their descriptions, and the level probabilities show how the judgment is distributed.
For severity, describe the difference between cosmetic impact, a usable workaround and a blocked task. A fractional score can help prioritize or aggregate judgments, while selecting the most probable category is a different operation. TypeSafe’s edition-specific guide warns that Score is weak for reconstructing an exact physical or numerical quantity by interpolating between levels. Keep precise arithmetic and measurements outside the model.
Noul returns the probability, from 0 to 1, that a defined condition is true. Optional true and false criteria clarify the boundary. It has no separate confidence field. A probability near 0.5 indicates uncertainty about yes versus no, not a middle value on a graded scale.
Choice and Score confidence are derived from their own distributions. For Choice with at least two options (n > 1) and selected probability p_max, the documented formula is (p_max − 1/n) / (1 − 1/n): it compares the top outcome with an even split. Score confidence also accounts for the probability-weighted distance from the most likely level, normalized against the spread of a uniform distribution and floored at 0. Thus adjacent ambiguous levels and opposite-end ambiguity have different meanings. Keep the full distribution when the task needs more detail than a single statistic.
Questions in one request see the same state and are evaluated independently. A result from one question is not hidden context for another. Split a broad judgment into focused concerns, then interpret or combine the returned values according to the task. An issue can have a category, an impact rating and a relevance check without turning those independent criteria into one vague priority label.
If a later question needs evidence fetched or options chosen from an earlier result, make that dependency explicit in a later request. For candidate extraction, first obtain the available values from the source, then use a bounded Choice to select among them. Jev 1.13 is not trained for free-form text generation and should not be described as producing an arbitrary new string or a narrative explanation.
The maker lists a 64k-token budget for the state plus all questions combined, and a 32k-token budget for the state plus the longest single question. Both constraints matter. A state that fits the total budget can still leave too little room for an individual question’s instructions and options. Remove unrelated material while keeping the evidence that determines the answer.
English is the edition’s primary training language and the producer reports its best accuracy there. Other languages, including CJK scripts, are accepted but do not have equal accuracy. Use representative source material from the intended language when assessing how probabilities or category boundaries should be interpreted. A text-only input contract does not establish universal multilingual performance.
TypeSafe documents literal reading of scoping words and negations, unreliable counting and arithmetic, difficulty comparing dates as ordered quantities, and reduced reliability with multiple layers of indirection. It recommends doing exact computation in code and giving the model the semantic judgment. Numerical encodings can be less effective than meaningful names, and a large state filled with unrelated detail can distract from the relevant evidence.
The same guide says adversarial content in state can steer the answer; contradictory instructions and criteria can confuse it; and Choice option order can sometimes bias a result toward an early option. Define the actual condition, align instructions with criteria, reduce unnecessary hops, and compare borderline judgments against the source. Keep the Jev 1.13 limits in mind when interpreting its judgments.
A useful Jev 1.13 artifact preserves the state identifier, complete question, options or levels, typed result, probabilities and relevant confidence statistic. Keep the version explicit when results or thresholds depend on this edition. Review uncertain cases against the evidence and let the application perform exact calculations and workflow actions; the model supplies a focused judgment with numerical uncertainty.
POST /v1/systemonetextdecisions| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits ~typesafe/jev-latest | Default— |
Fieldprovider | Typeschema | RequirementOptional | Values & limits | Default— |
Fieldquestions | Typeobject | RequirementRequired | Values & limits | Default— |
Fieldsession_id | Typestring | RequirementOptional | Values & limits | Default— |
Fieldstate | Typeschema | RequirementRequired | Values & limits | Default— |
Fieldtrace | Typeschema | RequirementOptional | Values & limits | Default— |
Fielduser | Typestring | RequirementOptional | Values & limits | Default— |
Fieldquestions.<id>.type | Typestring | RequirementRequired | Values & limits noul, choice, score | Default— |
Fieldquestions.<id>.instructions | Typestring|object|array | RequirementRequired | Values & limits | Default— |
Fieldquestions.<id>.criteria | Typeobject|array | RequirementOptional | Values & limits Conditions: choice/score: required; noul: optional. choice criteria is object; score is array with minItems1. | Default— |
Fieldquestions.<id>.criteria.true | Typestring|object|array | RequirementRequired | Values & limits Applies when: noul criteria object supplied | Default— |
Fieldquestions.<id>.criteria.false | Typestring|object|array | RequirementRequired | Values & limits Applies when: noul criteria object supplied | Default— |
noul · Required: state, questions.<id>.type=noul, questions.<id>.instructions
choice · Required: state, questions.<id>.type=choice, questions.<id>.instructions, criteria object
score · Required: state, questions.<id>.type=score, questions.<id>.instructions, criteria array with minItems1
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, state, questions |
Parametermaterial_types | Contracttext |
Parameteroptional_controls | Contractprovider, session_id, trace, user |
Parametermultimodal_input_binding | Contractnull |
Lifecycle: synchronous
Send the exact model ID and retain the complete native response.
Tariff references do not add request options. Supported parameters are listed for the selected method.
Match each charge to the conditions shown. Use one rate for each set of alternative configurations.
| Configuration | Rate schedule | Context tokens, more than | Context tokens, up to and including | Charge |
|---|---|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Context tokens, more than— | Context tokens, up to and includingNo upper bound | Charge Input · Input tokens $0.000084 / 1K tokens Output · Output tokens $0 / 1K tokens Input · Cache read — / 1K tokens Input · Cache write — / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
| ConfigurationRequest-length tier 1 | Rate schedule— | Context tokens, more than0 | Context tokens, up to and includingNo upper bound | Charge Input · Input tokens $0.000084 / 1K tokens Output · Output tokens $0 / 1K tokens Input · Cache read — / 1K tokens Input · Cache write — / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
{\n "model": "~typesafe/jev-latest",\n "questions": {\n "is_bug": {\n "criteria": {\n "false": "The customer is asking a question or requesting a feature.",\n "true": "The customer describes broken or unexpected product behavior."\n },\n "instructions": "Is the customer reporting a software defect?",\n "type": "noul"\n },\n "team": {\n "criteria": {\n "account": "Login, permissions, or profile issues.",\n "frontend": "Rendering, layout, or browser compatibility issues.",\n "payments": "Checkout, billing, or payment processing issues."\n },\n "instructions": "Which team should own this ticket?",\n "type": "choice"\n },\n "urgency": {\n "criteria": [\n "Can wait for the next release",\n "Should be fixed this week",\n "Blocking revenue right now"\n ],\n "instructions": "How urgent is this ticket?",\n "type": "score"\n }\n },\n "state": {\n "customer_tier": "enterprise",\n "ticket": "My checkout page shows a blank screen after I click Pay. I have tried two browsers."\n }\n}set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\n: "${AILOOT_REQUEST_FILE:?Set your actual JSON request file}"\nexport AILOOT_REQUEST_FILE\npython3 - <<'PY_REQUEST'\nimport json,os\nfrom pathlib import Path\np=json.loads(Path(os.environ['AILOOT_REQUEST_FILE']).read_text(encoding='utf-8'))\nif not isinstance(p,dict): raise SystemExit('Request must be a JSON object')\np['model']='~typesafe/jev-latest'\nPath('request.json').write_text(json.dumps(p,ensure_ascii=False),encoding='utf-8')\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/systemone \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o result.json\npython3 - <<'PY_RESULT'\nimport json\nfrom pathlib import Path\nprint(json.dumps(json.loads(Path('result.json').read_text()),ensure_ascii=False,indent=2))\nPY_RESULT\njson
Keep every complete returned response, file and content part.
Every supplied question-ID answer with its exact type, noul/choice/score value, confidence, probabilities and legend is retained. Entire original JSON is stored and returned only after settlement.
Preserve original operation and full/partial reply; do not replay POST.
| Field | Type |
|---|---|
Fieldmodel | Typestring |
Fieldid | Typestring |
Fieldprovider | Typestring |
Fieldanswers.<id>.type | Typestring |
Fieldanswers.<id>.noul | Typenumber |
Fieldanswers.<id>.choice | Typestring |
Fieldanswers.<id>.score | Typenumber |
Fieldanswers.<id>.confidence | Typenumber |
Fieldanswers.<id>.probabilities | Typeobject |
Fieldanswers.<id>.legend | Typeobject |
Fieldusage.input_tokens | Typeinteger |
Fieldusage.output_tokens | Typeinteger |
Fieldusage.cost | Typenumber |
| Response | Condition | Next step |
|---|---|---|
Response400 · invalid_request_error | ConditionInvalid required field, representation or value | Next stepCorrect the indicated request field. |
Ailoot Ultra typesafe/jev-1.13, ~typesafe/jev-latest
Use the method paths shown above.