Granite 4.2 30B vs SOMA X v0.3.0

At a Glance

Compare
Pricing and Limits
Input priceFrom · USD / 1M tokens$0.16Deepinfra · Sep 22, 2026Not reported
Output priceFrom · USD / 1M tokens$0.65Deepinfra · Sep 22, 2026Not reported
Context windowMaximum documented tokens131KNot reported
Model facts checkedSep 2, 2026View model evidence →Sep 2, 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

FieldGranite 4.2 30BSOMA-X v0.3.0
DeveloperIBMNVIDIA
FamilyGranite 4 2Soma X
ModelGranite 4.2 30BSOMA-X v0.3.0
VersionGranite 4.2 30BSOMA-X v0.3.0
Lifecycleactiveactive
Released2026-08-252026-09-02
Knowledge cutoffUnknownUnknown
Input modalitiesTextModel-specific input
Output modalitiesText3D
Context window131KUnknown
Total parameters29.3BUnknown
Active parametersUnknownUnknown
Licenseapache-2.0apache-2.0
Open weightsYesYes
API availableYesNo
Self-hostableYesYes
Provider accessDeepinfra (Standard)Unknown
Capabilitieschat, generation, reasoning, structured_outputs, toolsanimation, hand-modeling, human-body-modeling, motion-retargeting, pose-inversion, simulation

Granite 4.2 30B Capabilities

chatgenerationreasoningstructured outputstools
Serving providers1
Canonical IDibm-granite/granite-4.2-30b

SOMA X v0.3.0 Capabilities

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

Primary Evidence

Sources and Freshness

Questions

Granite 4.2 30B vs SOMA X v0.3.0 FAQs

Is Granite 4.2 30B or SOMA X v0.3.0 better for coding?+

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

Which is cheaper, Granite 4.2 30B or SOMA X v0.3.0?+

Only Granite 4.2 30B has a directly sourced input price: $0.16 per million tokens. Only Granite 4.2 30B has a directly sourced output price: $0.65 per million tokens.

Which has a larger context window, Granite 4.2 30B or SOMA X v0.3.0?+

Neither model has a larger sourced context window in this comparison. Granite 4.2 30B is 131K and SOMA X v0.3.0 is —.

Which performs better in benchmarks, Granite 4.2 30B or SOMA X v0.3.0?+

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

Can Granite 4.2 30B or SOMA X v0.3.0 be self-hosted?+

Both models have the same recorded self-hosting status: supported. Granite 4.2 30B is open weight; SOMA X v0.3.0 is open weight.

Can Granite 4.2 30B and SOMA X v0.3.0 understand images?+

Granite 4.2 30B is not documented with image input; SOMA X v0.3.0 is not documented with image input. This reflects supported input modalities, not vision quality.

Which can generate longer answers, Granite 4.2 30B or SOMA X v0.3.0?+

Neither has a larger sourced maximum output. Granite 4.2 30B is — and SOMA X v0.3.0 is —.

Do Granite 4.2 30B and SOMA X v0.3.0 support reasoning and tool use?+

Granite 4.2 30B: reasoning and tool calling. SOMA X v0.3.0: none of these features are definitively sourced. Feature support does not establish relative quality.

Which is available from more inference providers, Granite 4.2 30B or SOMA X v0.3.0?+

Granite 4.2 30B has 1 sourced provider route; SOMA X v0.3.0 has 0, so Granite 4.2 30B has broader tracked availability.

Which offers better value, Granite 4.2 30B or SOMA X v0.3.0?+

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