Calibrated per-label probabilities for routing, tagging and intent detection, with 1M-token text, image and PDF input.
Output Speed *
Intelligence Index *
Context Window *
Input price
Output price
Performance
Label Probabilities Over 1M Tokens, Without Generating Output
Benchmarks
classify-1 Benchmarks: Small Independent Tests, No Public Leaderboard Yet
Output Speed
Intelligence Index
MMLU *
GPQA *
HLE *
LiveCodeBench *
Technical Specifications
What the model supports
Limitations & Trade-offs
Best-Fit Workloads
Where this model earns its place
Intent routing and ticket triage
Per-label probabilities let a router send confident cases straight to a queue or model and flag the rest. An independent test scored 97.3% on CLINC150 and 92.7% on support tickets, with each label written as one plain-English line. This fits support routing, chatbot intent detection and model-selection gates. Keep label sets under 20 and include an out-of-scope label.
Long-document and scanned-file tagging
The document path takes one base64 JPEG, PNG, TIFF or PDF per request and returns the extracted text with the scores. Inputs can reach 1M tokens (vendor-stated). That suits contract-type detection, invoice-versus-report sorting and policy routing without a chunking layer. Cost and latency grow with document size and label count, and only one document is accepted per request.
Agent guardrails and loop detection
OpenRouter's classify-1 documentation links a cookbook for detecting stuck and looping agents. LangChain's integration post describes running Classify on a model's output and for runtime model routing. The one-sentence reason helps explain why a run was stopped. This fits long-running agents that need a cheap decision at every step. The reason is generated after the label, so trigger on the score.
Confidence-gated automation with human review
With a catch-all label and a 0.8 cutoff, ScaleDown's own CLINC150 test auto-handled 76% of messages at 99.6% accuracy and sent the rest to review. Multi-label mode adds independent tags per input, up to 16 labels. This pattern suits moderation, compliance tagging and queue prioritization. The result is vendor-reported on a simplified per-domain label set, so recalibrate the cutoff on your own data.