We use cookies. Cookies and browser storage keep you signed in and remember your preferences. With your permission we also measure how the site is used. You can any time. See our cookie policy.

New here? See how it works A 1-minute tour of the playground, models and your API key.

Microsoft-Decision-1 vs Drex Max: API price, context & features · api14

Microsoft: Microsoft-Decision-1 vs Nace.AI: Drex Max

A side-by-side comparison of Microsoft: Microsoft-Decision-1 ($0.15 / 1M tokens) and Nace.AI: Drex Max ($0.21 / 1M tokens) using current USD prices and capabilities from the api14 catalog. Both run through the same OpenAI-compatible API.

Specifications

	Microsoft: Microsoft-Decision-1	Nace.AI: Drex Max
Provider	Microsoft	Nace.AI
Input	$0.15 / 1M tokens	$0.21 / 1M tokens
Cache read	-	$0.21 / 1M tokens
Context window	32,768	262,144
Max output	29,491	235,929
Input	text	text, image
Output	decisions	decisions
Tool calling
Structured output
Reasoning control
Added	Oct 9, 2026	Oct 21, 2026

Key differences

Microsoft: Microsoft-Decision-1 is 30% cheaper on input tokens.
Nace.AI: Drex Max reads 8.0× more context (262,144 tokens).
A request with 1,000 input and 500 output tokens costs $0.000147 with Microsoft: Microsoft-Decision-1 and $0.000210 with Nace.AI: Drex Max.

In depth

Microsoft: Microsoft-Decision-1 is a decisions model from Microsoft, listed under the model id microsoft/microsoft-decision-1. Nace.AI: Drex Max is a decisions model from Nace.AI, listed under the model id nace-ai/drex-max. Both belong to the same category, so they are built for the same broad job: taking input and returning a decision rather than free form prose. Microsoft released its model on 2026-10-09, and Nace.AI released Drex Max on 2026-10-21, so both are recent entries in this category.

The clearest split between them is context and input handling. Drex Max has the bigger context window at 262144 tokens, while Microsoft-Decision-1 sits at 32768 tokens. Drex Max also accepts text and image input, whereas Microsoft-Decision-1 accepts text only. Both return decisions as their output modality, and neither lists supported parameters, so there is no difference to weigh there. On price, Microsoft-Decision-1 is the cheaper of the two on input; the comparison data does not show a meaningful difference on output pricing, so treat output cost as roughly comparable. In short, Drex Max gives you more room and an extra input modality, and Microsoft-Decision-1 gives you a lower input cost.

For practical selection, the deciding factor is usually how much material the model must read before it decides. If your decision depends on a long document, a large transcript, or a mix of text and screenshots or scanned pages, Drex Max is the natural fit because it takes image input and holds far more context in one call. If your inputs are short text prompts and cost per input token matters to you, Microsoft-Decision-1 is the better default, since it is the cheaper option on input and its 32768 token window is ample for compact decision tasks. Where both can handle the job, start with the cheaper input model and move up only when you actually hit the context limit or need to pass an image.

Calling either model through api14 works the same way, because the gateway exposes an OpenAI-compatible API. You point your existing OpenAI client at the api14 base URL, send your request to the chat completions endpoint, and set the model field to the id you want. Switching between the two is a one line change: use microsoft/microsoft-decision-1 for the Microsoft model, or nace-ai/drex-max for the Nace.AI model. Your request and response handling stay the same, and since neither model lists supported parameters, keep your payload to the standard fields and avoid relying on extra tuning options.

There is one case where the more expensive input model is still the right call even if you do not need images: when a single decision requires more than 32768 tokens of context. Microsoft-Decision-1 cannot hold that much in one request, so a long input would have to be trimmed or split, which can change the decision. Drex Max handles that volume directly. Otherwise, for short text only decision tasks, Microsoft-Decision-1 remains the sensible pick on input cost.

Switch with one string

Both models use the same endpoint and request shape. Change the model value from "microsoft/microsoft-decision-1" to "nace-ai/drex-max" and prompts, streaming and tools keep working.

Microsoft: Microsoft-Decision-1 details & playground →Nace.AI: Drex Max details & playground →

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": "nace-ai/drex-max",
  "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);

Microsoft: Microsoft-Decision-1 vs Nace.AI: Drex Max

Specifications

Key differences

In depth

Switch with one string

More comparisons