OpenAI's decision endpoint, announced at DevDay 2026. It focuses GPT-6 Luna on developer-defined questions that have a finite set of predefined answers, with text or image context, for classification, routing and an agent's next action.
Juspay's open decision model. Qwen3.6-35B-A3B with a merged rank-16 LoRA, shipped with a pinned SGLang serving bundle that answers Choice, Score and Noul questions over text, images or a video through a TypeSafe-compatible /v1/systemone API.
Decides
choice, classify, route
choice, score, noul, classify, route
Architecture
gpt-6-luna
xor
Fine-tuned from
—
qwen/qwen3.6-35b-a3b
License
proprietary
apache-2.0
Availability
Hosted API
Open weights
Hosted by
OpenAI
—
Input price
—
—
Decision accuracy
—
90.0%
Calibration error
—
0.073
Valid action rate
—
—
Median latency
—
69 ms
p95 latency
—
162 ms
Evaluation suite
Figures are from each model’s manifest; accuracy and latency are what the publishers report, on their own suites and hardware. Add a third model.
Questions
What is the difference between decisions-api and xor?
decisions-api is from OpenAI and xor from Juspay. decisions-api is only available as a hosted API; xor has open weights you can download and run. Both answer choice, classify and route questions. Only xor answers score and noul. decisions-api is licensed proprietary; xor, apache-2.0.
Which is more accurate, decisions-api or xor?
Only xor publishes an accuracy figure (90.0% on JevBench public set (231 items), maker's self-run of Xor 1.2); decisions-api does not, so there is no comparison to make without your own test.
Which is cheaper, decisions-api or xor?
decisions-api: Hosted, price not published. xor: Free (open weights). Open weights cost nothing per call beyond your own hardware.
Can I run decisions-api or xor locally?
xor yes — systemone pull juspay/xor downloads its weights. The other is only served as a hosted API.
—
JevBench public set (231 items), maker's self-run of Xor 1.2
