Compare · Last verified 2026-10-15

Microsoft-Decision-1 vs Jev: pricing, limits, and which to use

Verdict

On 2026-10-15 both list $0.042 per 1M input tokens with free output, and both use the System One question types (noul, choice, score). Jev has the larger context (64k default, 262k long-context vs 32,768 for Microsoft-Decision-1 on OpenRouter) and pinnable versions; Microsoft-Decision-1 wins if you need Azure Foundry deployment, Entra ID auth, and regional data zones.

Pick Microsoft-Decision-1 for: Azure shops that need Foundry deployments, Entra ID, and DataZoneStandard regions.
Pick Jev for: Long text state (over 32k tokens) and teams that want explicit version pinning.

Side-by-side

	Microsoft-Decision-1	Jev (TypeSafe AI)
Vendor	Microsoft (Foundry)	TypeSafe AI
Category	Decision model	Decision model
Price	$0.042 per 1M input tokens; output $0 (OpenRouter listing, provider Azure). [Verified 2026-10-15 on OpenRouter; Foundry/Azure price page not checked]	$0.042 per 1M input tokens ($42 per billion) for both Jev 1.14 and 1.13; output tokens free. Long-context mode costs the same per token. [Verified 2026-10-15 on docs.typesafe.ai/models]
Limits	32,768-token context window (OpenRouter). [Verified 2026-10-15 on OpenRouter] Rate limits are per deployment quota (429 on exceed); specific numbers not published on the how-to page. [Verified 2026-10-15 against official page]	64k tokens per request / 32k per question by default; 262k for both with the opt-in long-context header (slower and less accurate per TypeSafe). [Verified 2026-10-15 on docs.typesafe.ai/models]
Status	Released Oct 9, 2026 (OpenRouter). OpenRouter reported 99.99% availability over 3 days on 2026-10-15. [Verified 2026-10-15 on OpenRouter] OpenRouter: "Weights are updated continually while the API shape stays the same." Microsoft docs list model version 1. [Verified 2026-10-15; whether Foundry pins weights per version is unclear] Preview label and any SLA. [Unverified — not confirmed on a Microsoft page]	Jev 1.14 available from October 14, 2026 per TypeSafe docs. [Verified 2026-10-15 on docs.typesafe.ai/models] Correction: an earlier version of this page showed $0.42/1M taken from jevtypesafeai.com, a domain we could not tie to TypeSafe. TypeSafe’s own docs show $0.042. [Correction logged 2026-10-15]
Fit notes	Good fit: gates, routing, ranking, grading, and agent/tool selection inside a fixed allowlist. Microsoft lists known risks: bias, wording/order sensitivity, calibration strongest on familiar tasks, no explanations, may miss harmful content. Microsoft: for consequential decisions about people (credit, employment, housing, healthcare, legal) use it for decision support with meaningful human review, not as the sole decision-maker. Recommended: include a "cannot tell" option, randomize option order, and set thresholds from labeled data.	Pin a versioned ID (e.g. jev-1.13.0) rather than an alias so thresholds don’t drift with version changes. Text-oriented; check image support for your version in TypeSafe docs before relying on it.

FAQ

Are Microsoft-Decision-1 and Jev the same price?

As of 2026-10-15 both list $0.042 per 1M input tokens with no output charge (Microsoft-Decision-1 price taken from OpenRouter, provider Azure).

Which has the bigger context window?

Jev: 64k tokens per request by default and 262k with the long-context header. Microsoft-Decision-1: 32,768 tokens on OpenRouter.

Do they use the same API shape?

Both use System One-style typed questions (noul, choice, score). Endpoints and auth differ: Foundry /providers/microsoft/v1/systemone vs api.typesafe.ai/v1/systemone.

Methodology

Every fact in the table is copied from the vendor's official page (or OpenRouter where noted) and labeled with the date it was last verified. Items we could not confirm are marked unverified. Prices are list prices per 1M input tokens before regional or volume adjustments. See our methodology.