SOMA X v0.3.0 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 2, 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 →

Different Model RolesThese models do not share a sourced market category. Their primary-source facts remain comparable below, while performance claims require matched evidence.

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

FieldSOMA-X v0.3.0Jev
DeveloperNVIDIATypeSafe
FamilySoma XJev
ModelSOMA-X v0.3.0Jev
VersionSOMA-X v0.3.0Jev
Lifecycleactiveactive
Released2026-09-022026-09-15
Knowledge cutoffUnknownUnknown
Input modalitiesModel-specific inputText, Model-specific input
Output modalities3DModel-specific input
Context windowUnknown64K
Total parametersUnknownUnknown
Active parametersUnknownUnknown
Licenseapache-2.0Unknown
Open weightsYesNo
API availableNoYes
Self-hostableYesNo
Provider accessUnknownTypeSafe (Standard)
Capabilitiesanimation, hand-modeling, human-body-modeling, motion-retargeting, pose-inversion, simulationcalibrated-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

SOMA X v0.3.0 Capabilities

animationhand-modelinghuman-body-modelingmotion-retargetingpose-inversionsimulation
Serving providers0
Canonical IDnvidia/SOMA-X-v0.3.0

Jev Capabilities

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

Primary Evidence

Sources and Freshness

Questions

SOMA X v0.3.0 vs Jev FAQs

Is SOMA X v0.3.0 or Jev better for coding?+

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

Which is cheaper, SOMA X v0.3.0 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, SOMA X v0.3.0 or Jev?+

Neither model has a larger sourced context window in this comparison. SOMA X v0.3.0 is — and Jev is 64K.

Which performs better in benchmarks, SOMA X v0.3.0 or Jev?+

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

Can SOMA X v0.3.0 or Jev be self-hosted?+

SOMA X v0.3.0 is the only model in this pair currently marked as self-hostable. SOMA X v0.3.0 is open weight; Jev is not marked open weight.

Can SOMA X v0.3.0 and Jev understand images?+

SOMA X v0.3.0 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, SOMA X v0.3.0 or Jev?+

Neither has a larger sourced maximum output. SOMA X v0.3.0 is — and Jev is —.

Do SOMA X v0.3.0 and Jev support reasoning and tool use?+

SOMA X v0.3.0: 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, SOMA X v0.3.0 or Jev?+

SOMA X v0.3.0 has 0 sourced provider routes; Jev has 1, so Jev has broader tracked availability.

Which offers better value, SOMA X v0.3.0 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