Favicon for togethercomputer

Together: Tev1 4B Experimental

togethercomputer/tev1-4b-experimental

Model weights

Tev1 4B Experimental is an experimental decision model from Together AI, a supervised fine-tune of Qwen3.5-4B trained to choose one option from a structured state, question, and list of 2-24 labeled options. It keeps Qwen's standard next-token head, so it is served through the regular chat completions API rather than a dedicated decisions runtime.

Send a system instruction followed by a JSON decision containing state, question, and options. The model returns a single option letter, which application code maps back to the option key. Recommended settings are temperature: 0, max_tokens: 8, and thinking disabled. It is intended for routing, classification, and policy checks, not generic chat. Together publishes the full data recipe and training code so teams can fine-tune their own variant.

Modalities
In / out price
$0.042 / $0per 1M
Context
33K
Released
Sep 30, 2026

Playground

Providers

This model is hosted by one provider. OpenRouter forwards every request without routing.

Pricing

The average price customers actually pay for this model, next to the prices providers post. Caching and discounts mean the price actually paid is often well below the listed one.

Weighted average

Input
$0.04186/M tokens
Output
$0/M tokens
Price history
No effective price data for this selection

Performance

Latency is how long it takes to return the full response (lower is better).

Latency
0.18s

P50, best provider

Uptime

Uptime is the percentage of the past 3 days that at least one provider was responding to requests. Availability is the percentage of time that inference was successfully served. OpenRouter continuously monitors and uses the next-best provider when one returns an error.

Uptime (3d)The model was reachable. Request routed to a provider.
99.99%
Availability (3d)The model returned inference from any provider. Errors and empty responses count against it.
92.87%

Availability over the last 3 days

Last 72 hours
Availability 92.87%
3 Days Ago2 Days AgoYesterdayNow

Availability over the last 24 hours

OpenRouter Availability
84.23%

When an error occurs in an upstream provider, we can recover by routing to another healthy provider, if your request filters allow it. You can access per-provider uptime data programmatically through the Endpoints API. Learn more about our load balancing and provider routing options.

Apps

Public apps that send the most traffic to this model. Good signal for what real production workloads look like — and a hint at which use cases this model is best suited for.

1.
42.8Mtokens
2.
28.8Mtokens
3.
19.9Mtokens
5.
7.03Mtokens
Rest of OpenRouter
49.3M
Top 5 Apps
219K

Activity

Token volume and request traffic to this model over time.

API

Drop-in code to call this model. It runs on the OpenRouter Decisions API rather than the OpenAI-compatible chat endpoint, so the request and response shapes below are specific to structured decisions — chat completions SDKs will not work with it.

Not currently available through EU in-region routing. In-region routing docs

Documentation

Guides, cookbooks, blog posts, and tools for building with Together: Tev1 4B Experimental on OpenRouter.

Frequently asked questions