Tev1 4B Experimental is Together AI’s classification model for questions with a fixed answer set. The manufacturer fine-tuned it from Qwen3.5 4B and reports 4.7 billion parameters. It uses non-thinking text generation to select an option: the documented input is a state, one question and labeled choices, and the requested output is exactly one letter. The application maps that letter to the option’s semantic key. This separates its decision workflow from a model that directly returns calibrated probabilities or an expected rubric score.
The producer’s interface represents the decision as a JSON object with state, question and options. Each option contains a letter label from A through X, a semantic key and a description. Supply between two and 24 options and make each description explain when that answer applies. A letter is the compact output label; the semantic key is the meaning the surrounding software uses. Keep the mapping associated with the exact option list used for that decision.
For a support message, the state should contain the message and relevant context, while the question defines which intent or destination to choose. An illustrative list can distinguish a reported integration failure, an access issue and a product-information request, with a none option when the listed intents do not fit. Define overlapping cases rather than expecting the model to infer the organization’s routing policy from abbreviated labels.
Together’s published example supplies a system instruction that treats content inside state as data, selects one listed option and requests only its letter with no explanation. Its recommended settings are temperature 0, an eight-token generation allowance and thinking disabled. The maker explicitly says these settings are not injected automatically by the public endpoint; the example helper supplies them, while a direct request must specify them. Use these settings to request the intended short, non-thinking classification response.
The eight-token allowance is an example output setting for this short-answer workflow, not a universal maximum output specification. The intended useful output remains the selected letter. If a helper exposes a label-and-key object afterward, distinguish that interpreted object from the model’s raw generated content. A category selection does not itself update a ticket, approve an operation or execute the next action.
The maker describes intent detection, policy application, workflow routing, document categories, sentiment and passage-based yes/no comprehension as supported task patterns. A boolean task can supply two options whose keys mean true and false; the application interprets the selected option accordingly. A sentiment task can supply described levels and return the key for one selected category. That categorical choice is not a probability-weighted average across levels, and a returned letter is not a numerical confidence value.
For a rule-based decision, include the relevant facts and the rule in the task rather than asking the model to invent the policy. For example, a document-routing brief can describe the permitted folders and the material that belongs in each. A research-taxonomy task can provide a paper’s title and abstract together with topic descriptions. The result should be interpreted against the supplied alternatives, with the original evidence retained for an ambiguous or disputed choice.
The model page records 37,840 training examples covering entailment, passage yes/no questions, banking intents, news categories, sentiment levels, programmatic policies, routing and research-paper taxonomy. The companion guide documents normalizing these tasks into a shared decision format and fine-tuning a classification model. This explains the profile’s focus on a bounded answer set; it does not establish that every new policy, domain or taxonomy will be handled correctly without task-specific assessment.
Tev1 4B Experimental is the named Together model, not the general Qwen3.5 4B base profile and not a checkpoint from another decision-model maker. Retain the experimental edition’s own output preparation and input contract. A common decision use case or a familiar base family does not justify borrowing another model’s image support, probability calibration, tool calls or question-batching limits.
Together’s model specification reports a 32.8K-token context window and text input with text output. The context has to accommodate the instructions, state, question and options used in the classification request. Prepare only the evidence the question needs, while retaining the definitions that distinguish the alternatives. Keep the classification prompt compact by removing irrelevant context while retaining the option definitions.
The producer identifies this as an experimental release intended for assessment on real decision workloads. Check that the raw response is one of the supplied labels before mapping it to a semantic key, and compare classifications with representative labeled material from the intended task. A valid letter establishes a well-formed selection, not proof that its interpretation is correct. Keep the input, options, returned letter and mapped key together so the final artifact can support routing, categorization or policy review without losing how the decision was defined.
", "aboutText": "Tev1 4B Experimental is Together AI’s classification model for questions with a fixed answer set. The manufacturer fine-tuned it from Qwen3.5 4B and reports 4.7 billion parameters. It uses non-thinking text generation to select an option: the documented input is a state, one question and labeled choices, and the requested output is exactly one letter. The application maps that letter to the option’s semantic key. This separates its decision workflow from a model that directly returns calibrated probabilities or an expected rubric score.\n\n### State, question and 2–24 options\n\nThe producer’s interface represents the decision as a JSON object with state, question and options. Each option contains a letter label from A through X, a semantic key and a description. Supply between two and 24 options and make each description explain when that answer applies. A letter is the compact output label; the semantic key is the meaning the surrounding software uses. Keep the mapping associated with the exact option list used for that decision.\n\nFor a support message, the state should contain the message and relevant context, while the question defines which intent or destination to choose. An illustrative list can distinguish a reported integration failure, an access issue and a product-information request, with a none option when the listed intents do not fit. Define overlapping cases rather than expecting the model to infer the organization’s routing policy from abbreviated labels.\n\n### Non-thinking generation and the requested answer shape\n\nTogether’s published example supplies a system instruction that treats content inside state as data, selects one listed option and requests only its letter with no explanation. Its recommended settings are temperature 0, an eight-token generation allowance and thinking disabled. The maker explicitly says these settings are not injected automatically by the public endpoint; the example helper supplies them, while a direct request must specify them. Use these settings to request the intended short, non-thinking classification response.\n\nThe eight-token allowance is an example output setting for this short-answer workflow, not a universal maximum output specification. The intended useful output remains the selected letter. If a helper exposes a label-and-key object afterward, distinguish that interpreted object from the model’s raw generated content. A category selection does not itself update a ticket, approve an operation or execute the next action.\n\n### Classification, rules and categorical ratings\n\nThe maker describes intent detection, policy application, workflow routing, document categories, sentiment and passage-based yes/no comprehension as supported task patterns. A boolean task can supply two options whose keys mean true and false; the application interprets the selected option accordingly. A sentiment task can supply described levels and return the key for one selected category. That categorical choice is not a probability-weighted average across levels, and a returned letter is not a numerical confidence value.\n\nFor a rule-based decision, include the relevant facts and the rule in the task rather than asking the model to invent the policy. For example, a document-routing brief can describe the permitted folders and the material that belongs in each. A research-taxonomy task can provide a paper’s title and abstract together with topic descriptions. The result should be interpreted against the supplied alternatives, with the original evidence retained for an ambiguous or disputed choice.\n\n### Training scope and edition identity\n\nThe model page records 37,840 training examples covering entailment, passage yes/no questions, banking intents, news categories, sentiment levels, programmatic policies, routing and research-paper taxonomy. The companion guide documents normalizing these tasks into a shared decision format and fine-tuning a classification model. This explains the profile’s focus on a bounded answer set; it does not establish that every new policy, domain or taxonomy will be handled correctly without task-specific assessment.\n\nTev1 4B Experimental is the named Together model, not the general Qwen3.5 4B base profile and not a checkpoint from another decision-model maker. Retain the experimental edition’s own output preparation and input contract. A common decision use case or a familiar base family does not justify borrowing another model’s image support, probability calibration, tool calls or question-batching limits.\n\n### Context and reviewing the result\n\nTogether’s model specification reports a 32.8K-token context window and text input with text output. The context has to accommodate the instructions, state, question and options used in the classification request. Prepare only the evidence the question needs, while retaining the definitions that distinguish the alternatives. Keep the classification prompt compact by removing irrelevant context while retaining the option definitions.\n\nThe producer identifies this as an experimental release intended for assessment on real decision workloads. Check that the raw response is one of the supplied labels before mapping it to a semantic key, and compare classifications with representative labeled material from the intended task. A valid letter establishes a well-formed selection, not proof that its interpretation is correct. Keep the input, options, returned letter and mapped key together so the final artifact can support routing, categorization or policy review without losing how the decision was defined.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "7e519dbc681784698089ec0e8172a4ddc556f57b75f84b6246adadee895e887b", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "togethercomputer/tev1-4b-experimentalTev1 4B Experimental is Together AI’s text classifier for bounded decisions: give it a state, a question and 2–24 labeled options, and its documented output is one letter. The application maps that letter to a category key; it is not a native probability distribution or expected-score response.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Tev1 4B Experimental is Together AI’s classification model for questions with a fixed answer set. The manufacturer fine-tuned it from Qwen3.5 4B and reports 4.7 billion parameters. It uses non-thinking text generation to select an option: the documented input is a state, one question and labeled choices, and the requested output is exactly one letter. The application maps that letter to the option’s semantic key. This separates its decision workflow from a model that directly returns calibrated probabilities or an expected rubric score.
The producer’s interface represents the decision as a JSON object with state, question and options. Each option contains a letter label from A through X, a semantic key and a description. Supply between two and 24 options and make each description explain when that answer applies. A letter is the compact output label; the semantic key is the meaning the surrounding software uses. Keep the mapping associated with the exact option list used for that decision.
For a support message, the state should contain the message and relevant context, while the question defines which intent or destination to choose. An illustrative list can distinguish a reported integration failure, an access issue and a product-information request, with a none option when the listed intents do not fit. Define overlapping cases rather than expecting the model to infer the organization’s routing policy from abbreviated labels.
Together’s published example supplies a system instruction that treats content inside state as data, selects one listed option and requests only its letter with no explanation. Its recommended settings are temperature 0, an eight-token generation allowance and thinking disabled. The maker explicitly says these settings are not injected automatically by the public endpoint; the example helper supplies them, while a direct request must specify them. Use these settings to request the intended short, non-thinking classification response.
The eight-token allowance is an example output setting for this short-answer workflow, not a universal maximum output specification. The intended useful output remains the selected letter. If a helper exposes a label-and-key object afterward, distinguish that interpreted object from the model’s raw generated content. A category selection does not itself update a ticket, approve an operation or execute the next action.
The maker describes intent detection, policy application, workflow routing, document categories, sentiment and passage-based yes/no comprehension as supported task patterns. A boolean task can supply two options whose keys mean true and false; the application interprets the selected option accordingly. A sentiment task can supply described levels and return the key for one selected category. That categorical choice is not a probability-weighted average across levels, and a returned letter is not a numerical confidence value.
For a rule-based decision, include the relevant facts and the rule in the task rather than asking the model to invent the policy. For example, a document-routing brief can describe the permitted folders and the material that belongs in each. A research-taxonomy task can provide a paper’s title and abstract together with topic descriptions. The result should be interpreted against the supplied alternatives, with the original evidence retained for an ambiguous or disputed choice.
The model page records 37,840 training examples covering entailment, passage yes/no questions, banking intents, news categories, sentiment levels, programmatic policies, routing and research-paper taxonomy. The companion guide documents normalizing these tasks into a shared decision format and fine-tuning a classification model. This explains the profile’s focus on a bounded answer set; it does not establish that every new policy, domain or taxonomy will be handled correctly without task-specific assessment.
Tev1 4B Experimental is the named Together model, not the general Qwen3.5 4B base profile and not a checkpoint from another decision-model maker. Retain the experimental edition’s own output preparation and input contract. A common decision use case or a familiar base family does not justify borrowing another model’s image support, probability calibration, tool calls or question-batching limits.
Together’s model specification reports a 32.8K-token context window and text input with text output. The context has to accommodate the instructions, state, question and options used in the classification request. Prepare only the evidence the question needs, while retaining the definitions that distinguish the alternatives. Keep the classification prompt compact by removing irrelevant context while retaining the option definitions.
The producer identifies this as an experimental release intended for assessment on real decision workloads. Check that the raw response is one of the supplied labels before mapping it to a semantic key, and compare classifications with representative labeled material from the intended task. A valid letter establishes a well-formed selection, not proof that its interpretation is correct. Keep the input, options, returned letter and mapped key together so the final artifact can support routing, categorization or policy review without losing how the decision was defined.
POST /v1/systemonetextdecisions| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits togethercomputer/tev1-4b-experimental | 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": "togethercomputer/tev1-4b-experimental",\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']='togethercomputer/tev1-4b-experimental'\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 togethercomputer/tev1-4b-experimental
Use the method paths shown above.