Upstage
•
Solar Decide
•
Released 
September 2026

Upstage
Solar Decide

Returns typed choices, scores and yes/no answers with model-derived probabilities in one forward pass, instead of generated text.

Modality:
Text
model ID
upstage/solar-decide

Output Speed *

N/A
tok/s

Intelligence Index *

N/A
/ 100

Context Window *

524288
tokens

Input price

0.3
Anytoken

Output price

0
Anytoken
Solar Decide: Calibrated Decisions Instead of Generated Text Solar Decide is Upstage's structured decision model, served as a System One endpoint on Solar Mini 4. You send a state and typed questions. It returns a choice, a score or a yes/no answer, each with a probability read directly from the model. It generates no prose, and each question takes one forward pass. A 524,288-token context window lets a whole document serve as the state. It suits routing, classification and policy checks, especially with Korean content. Add Solar Decide to your routing layer via AnyAPI.ai

Performance

Single-Pass Decisions with Probabilities You Can Threshold

Solar Decide does not write an answer and then parse it. Upstage's documentation says it reads the decision from the logits of single-token labels, so each typed question is answered in one forward pass. Each answer carries a probability taken from the model, not text it generated. In practice you can set confidence thresholds, send low-confidence cases to a human or a stronger model, and skip output-parsing code. It runs on a 524,288-token context, so long documents can be classified without chunking. Independent accuracy figures are not yet published.

Technical Specifications

What the model supports

Solar Decide takes text as input and returns structured decisions, not generated text. Its context window is 524,288 tokens, and no conventional maximum-output setting applies because no prose is produced. The key production limit is the cap of 26 options per choice question. Larger label sets must be split into several questions or narrowed first, otherwise the API returns a 422 validation error. It uses Upstage's System One schema, not the chat-completions format, so existing chat client code won't work unchanged.
Verified Specifications — 
Solar Decide
*
Input modalities
Text
output modalities
Text
Context window
524288
 tokens
Maximum output tokens
471859
Reasoning
No
Knowledge cutoff
September 2026
Pricing (standard)
0.3
 AnyTokens in
 / 
0
 AnyTokens out

Comparison

Solar Decide or Solar Decide Flash for Routing and Policy Checks?

Solar Decide and Solar Decide Flash are the closest comparison because both are System One decision models built on Solar Mini 4. Both return typed answers with probabilities in a single forward pass, keep the 512K context window, and list the same input rate with free output tokens on OpenRouter. Upstage describes Flash as the faster, low-latency variant tuned for consistent response times. The decision is whether response-time consistency matters more than staying on the baseline model.

Dimension
Solar Decide
Solar Decide Flash
Context window *
524288
tokens
524288
tokens
Output speed *
N/A
tok/s
N/A
tok/s
Intelligence Index *
N/A
N/A
Input pricing
0.3
AnyToken
0.3
AnyToken
Output pricing
0
AnyToken
0
AnyToken
Knowledge cutoff *
September 2026
October 2026

Choose Solar Decide when you want the baseline decision model, are validating a decision pipeline in beta, or run asynchronous jobs such as batch document review where tail latency matters less. Choose Solar Decide Flash when decisions sit in a synchronous path, such as live ticket triage or request gating, and consistent response times matter. No published accuracy comparison between the two exists, so run both on your labeled data before committing.

Limitations & Trade-offs

Where Solar Decide falls short

1
No generated explanations. Solar Decide produces no prose, only choices, scores or yes/no answers with probabilities. That makes it unsuitable for drafting replies, summarizing, or explaining why a decision was made. Teams that need a rationale for audits or users must pair it with a generative model such as Solar Pro 4 or another chat model. Use Solar Decide for the decision step, not the explanation.
2
26-option ceiling. Choice questions accept 2 to 26 options because the endpoint scores single-token labels A through Z in one pass. A 27th candidate returns a 422 validation error. Large taxonomies, product catalogs, or fine-grained intent sets must be split into several questions or pre-filtered, adding pipeline logic and extra calls. For open-ended labeling, a generative model is simpler.
3
Beta status and no published accuracy data. Upstage lists Solar Decide as Beta, and no independent benchmarks of its accuracy or calibration were found. The probabilities come from the model's logits, but whether they are well calibrated on your data is unverified. Build a labeled evaluation set, check threshold behavior, and expect possible interface changes before adopting it for compliance-critical decisions.
4
Text-only input and a non-chat schema. Solar Decide accepts text, so scanned documents or images must be converted first, for example with a document-parsing step. It also uses the System One request format, not chat completions, so existing OpenAI-style chat clients and prompts won't work unchanged. Plan a dedicated integration path rather than swapping the model ID in a chat call.

Best-Fit Workloads

Where this model earns its place

01

Support ticket routing

‍
Upstage's own example sends a customer ticket as the state and asks typed questions about it. One call can decide the queue (up to 26 options), whether the customer wants a refund (yes/no), and an urgency score. Each answer arrives with a probability, so low-confidence tickets can go to a person. The 524K context window also covers long ticket threads. It does not write the reply.

02

Long-document policy and compliance checks

‍
Upstage positions the model for policy checks, and the 524,288-token context lets an entire document serve as the state. A contract or policy file can be tested against yes/no questions, such as whether a clause breaks a rule. The returned probability supports review thresholds. Because it produces no explanation, flagged items still need a reviewer or a generative model to cite the relevant passage.

03

Korean-language classification and moderation

‍
Upstage says Solar Decide brings Solar Mini 4's strong Korean understanding to routing, classification and policy checks. That makes it a candidate for Korean support content, community moderation and intent detection, where yes/no or category outputs are enough. No independent Korean benchmark for this endpoint has been published, so validate it on your own labeled Korean data.

04

Confidence-gated agent routing

‍
In an agent pipeline, Solar Decide can act as a gate before expensive model calls. It can pick a route, check a guardrail condition or score a request, then escalate only when the returned probability falls below a threshold. A single forward pass per question suits this role. It is a decision component, not a planner, and it does not call tools.

Pricing in anytokens via AnyAPI
Input
0.3
₳
Output
0
₳
Cache write
0
₳
Cache read
0.3
₳

Integration

Access Solar Decide via AnyAPI.ai

Access Solar Decide through AnyAPI.ai using a unified API built for multi-model AI applications. Integrate Solar Decide without maintaining a separate provider-specific connection, and keep the flexibility to test, switch, or combine models as your application requirements evolve.

01

One API integration

Access Solar Decide and other AI models through the same API workflow instead of maintaining separate integrations for every provider.

02

Easy model switching

Test Solar Decide against alternative models or switch models as your performance, capability, or cost requirements change without rebuilding your application around another provider API.

03

Flexible for production

Use Solar Decide from experimentation through production while keeping your AI stack flexible as workloads, traffic, and model requirements evolve.

04

Multi-model applications

Use Solar Decide for the workloads where it performs best and combine it with other models for tasks that require different capabilities, performance, or efficiency.

Frequently Asked Questions

Answers to common questions about integrating and using this AI model via AnyAPI.ai

Solar Decide is Upstage's structured decision model, served as a System One endpoint on Solar Mini 4. You send a state and typed questions, and it returns a choice, a score or a yes/no answer. Each answer comes with a probability taken from the model. It generates no prose, and Upstage lists it as Beta.

No. Solar Decide does not generate text and does not use the chat completions format. It uses Upstage's System One schema, which takes a model ID, a state and typed questions. Existing chat clients won't work unchanged. Use it for classification, routing and checks, and pair it with a chat model when you need written output.

Solar Decide has a context window of 524,288 tokens, which Upstage describes as 512K. That is large enough to use an entire document as the state for its questions. Maximum output tokens do not apply in the usual sense, because the model returns typed decisions instead of generated text.

A choice question accepts 2 to 26 options. The endpoint reads the decision from the logits of single-token labels A through Z, which sets the limit at 26. Sending 27 or more returns a 422 validation error. For larger label sets, split the decision into several questions or narrow the candidates first.

Solar Decide has a low input rate, and Upstage does not bill output tokens because no prose is generated. See the AnyTokens pricing component on this page for AnyAPI.ai rates. Upstage lists the model as Beta and no independent accuracy benchmarks exist yet, so validate it on your own labeled data before relying on it for critical decisions.

* Benchmark data source: Artificial Analysis artificialanalysis.ai