Nace.AI: Drex v1.5 vs ScaleDown: Classify-1
A side-by-side comparison of Nace.AI: Drex v1.5 ($0.14 / 1M tokens) and ScaleDown: Classify-1 ($0.14 / 1M tokens) using current USD prices and capabilities from the api14 catalog. Both run through the same OpenAI-compatible API.
Specifications
| Nace.AI: Drex v1.5 | ScaleDown: Classify-1 | |
|---|---|---|
| Provider | Nace.AI | ScaleDown |
| Input | $0.14 / 1M tokens | $0.14 / 1M tokens |
| Context window | 131,072 | 1,000,000 |
| Max output | 117,964 | 900,000 |
| Input | text | text, image, file |
| Output | decisions | decisions |
| Tool calling | ||
| Structured output | ||
| Reasoning control | ||
| Added | Oct 9, 2026 | Oct 13, 2026 |
Key differences
- Both have about the same input price.
- ScaleDown: Classify-1 reads 7.6× more context (1,000,000 tokens).
- A request with 1,000 input and 500 output tokens costs $0.000140 with Nace.AI: Drex v1.5 and $0.000140 with ScaleDown: Classify-1.
In depth
Nace.AI: Drex v1.5 is a decisions model from Nace.AI, released on 2026-10-09. ScaleDown: Classify-1 is a decisions model from ScaleDown, released on 2026-10-13. Both sit in the same category, so the choice between them is not about what kind of output you get, since both return decisions, but about what you feed them and how much you can feed them at once.
The clearest split is context and input modalities. Classify-1 accepts text, images and files, and its context window is the larger of the two at 1,000,000 tokens. Drex v1.5 takes text only and tops out at 131,072 tokens. Neither model lists supported parameters, so you should not expect tuning knobs beyond the basics of a request. On price, the two are about the same for input, and there is no meaningful difference recorded for output pricing, so cost is unlikely to be the deciding factor here.
For a developer choosing a call, the practical rule follows from those differences. If your input is plain text and fits comfortably inside roughly 131k tokens, Drex v1.5 covers the job and keeps you on a smaller, simpler payload. If you need to classify or decide over images, uploaded files, or very long documents such as full logs, contracts or multi-file bundles, Classify-1 is the one that can actually accept the input, and its larger window means fewer chunking and stitching steps on your side. Tasks that mix a screenshot with a question, or that span hundreds of pages of text, point to Classify-1 almost by default.
Calling either model through api14 works the same way because the gateway exposes an OpenAI-compatible API. You send your request to the same endpoint with the same request shape, and the only thing that changes is the model id: use "nace-ai/drex-v1.5" for Drex v1.5 and "scaledown/classify-1" for Classify-1. Your client code, authentication and response handling stay as they are, so switching between the two is a one-line change and you can route different workloads to different models without maintaining two integrations.
There is still a case for Drex v1.5 even when Classify-1 looks like the safer pick. If your pipeline is text only and already fits within its context limit, Drex v1.5 avoids sending image or file payloads you do not need, and since input pricing is about the same, there is no cost penalty for staying with it. Treat Classify-1 as the default when modality or length is in question, and Drex v1.5 as the lean choice for straightforward text decisions.
Switch with one string
Both models use the same endpoint and request shape. Change the model value from "nace-ai/drex-v1.5" to "scaledown/classify-1" and prompts, streaming and tools keep working.
import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://api14.com/api/v1",
apiKey: process.env.API14_API_KEY,
});
const result = await client.post("/decisions", { body: {
"model": "scaledown/classify-1",
"state": "Customer: I was charged twice for my order and want my money back.",
"questions": {
"team": {
"type": "choice",
"instructions": "Which team should handle this message?",
"criteria": {
"billing": "Payments, refunds, invoices",
"support": "Product questions and bugs",
"sales": "Pricing and new purchases"
}
},
"urgent": {
"type": "noul",
"instructions": "Does this need a reply today?",
"criteria": {
"true": "Money, outage or legal risk",
"false": "Can wait"
}
}
}
} });
console.log(result.answers);
More comparisons
- LiquidAI: d1 Latest vs LiquidAI: d1-ultra Latest
- LiquidAI: d1 Latest vs Baseten: Joey 1
- LiquidAI: d1 Latest vs LiquidAI: d1.1
- LiquidAI: d1 Latest vs Morph: Reflex
- LiquidAI: d1-ultra Latest vs Baseten: Joey 1
- LiquidAI: d1-ultra Latest vs LiquidAI: d1.1
- LiquidAI: d1-ultra Latest vs Morph: Reflex
- Baseten: Joey 1 vs LiquidAI: d1.1