MAI Transcribe 2 vs Jev

At a Glance

Compare
JevTypeSafe
Pricing and Limits
Input priceFrom · USD / 1M tokensNot reported$0.042TypeSafe · Sep 17, 2026
Output priceFrom · USD / 1M tokensNot reported$0.000TypeSafe · Sep 17, 2026
Context windowMaximum documented tokensNot reported64K
Model facts checkedSep 3, 2026View model evidence →Sep 17, 2026View model evidence →

Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →

Available Benchmarks

All benchmark results →
No Protocol-Matched Benchmark Yet.Results appear here only when both models share the same benchmark version, metric, evaluation protocol, and evidence class.

Side-by-Side Facts

FieldMAI-Transcribe 2Jev
DeveloperMicrosoftTypeSafe
FamilyMai TranscribeJev
ModelMAI-Transcribe 2Jev
VersionMAI-Transcribe 2Jev
Lifecyclepreviewactive
Released2026-09-032026-09-15
Knowledge cutoffUnknownUnknown
Input modalitiesAudioText, Model-specific input
Output modalitiesTextModel-specific input
Context windowUnknown64K
Total parametersUnknownUnknown
Active parametersUnknownUnknown
LicenseUnknownUnknown
Open weightsNoNo
API availableYesYes
Self-hostableUnknownNo
Provider accessMicrosoft Foundry (Public preview)TypeSafe (Standard)
Capabilitiesdiarization, multilingual, speaker-attribution, transcription, word-level-timestampscalibrated-confidence, parallel-evaluation, structured_outputs, typed-decisions
Maximum Choice cardinalityUnknown255 options
Default request rate limitUnknown1200 requests per minute
State plus longest question limitUnknown32000 tokens
Combined state and questions limitUnknown64000 tokens
Default token rate limitUnknown250000 tokens per second

MAI Transcribe 2 Capabilities

diarizationmultilingualspeaker-attributiontranscriptionword-level-timestamps
Serving providers1
Canonical IDmicrosoft/mai-transcribe

Jev Capabilities

calibrated-confidenceparallel-evaluationstructured outputstyped-decisions
Serving providers1
Canonical IDtypesafe/jev

Primary Evidence

Sources and Freshness

Questions

MAI Transcribe 2 vs Jev FAQs

Is MAI Transcribe 2 or Jev better for coding?+

This comparison does not currently contain a protocol-matched coding benchmark for both MAI Transcribe 2 and Jev, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.

Which is cheaper, MAI Transcribe 2 or Jev?+

Only Jev has a directly sourced input price: $0.042 per million tokens. Only Jev has a directly sourced output price: $0.000 per million tokens.

Which has a larger context window, MAI Transcribe 2 or Jev?+

Neither model has a larger sourced context window in this comparison. MAI Transcribe 2 is — and Jev is 64K.

Which performs better in benchmarks, MAI Transcribe 2 or Jev?+

There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.

Can MAI Transcribe 2 or Jev be self-hosted?+

Neither model is the only model in this pair currently marked as self-hostable. MAI Transcribe 2 is not marked open weight; Jev is not marked open weight.

Can MAI Transcribe 2 and Jev understand images?+

MAI Transcribe 2 is not documented with image input; Jev is not documented with image input. This reflects supported input modalities, not vision quality.

Which can generate longer answers, MAI Transcribe 2 or Jev?+

Neither has a larger sourced maximum output. MAI Transcribe 2 is — and Jev is —.

Do MAI Transcribe 2 and Jev support reasoning and tool use?+

MAI Transcribe 2: none of these features are definitively sourced. Jev: none of these features are definitively sourced. Feature support does not establish relative quality.

Which is available from more inference providers, MAI Transcribe 2 or Jev?+

MAI Transcribe 2 has 1 sourced provider route; Jev has 1, a tie.

Which offers better value, MAI Transcribe 2 or Jev?+

There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.

Send Feedback