MedGemma vs Stockmark 2 100B Instruct
MedGemma (2024) and Stockmark 2 100B Instruct (2025) are compact production models from Google DeepMind and Stockmark. MedGemma ships a not-yet-sourced context window, while Stockmark 2 100B Instruct ships a 128K-token context window. This comparison covers specs, pricing, capabilities, benchmarks, provider availability, and production fit. It focuses on practical selection signals rather than broad model-family marketing. The goal is to make the tradeoff clear before deeper testing.
Stockmark 2 100B Instruct is safer overall; choose MedGemma when vision-heavy evaluation matters.
Decision scorecard
Local evidence first| Signal | MedGemma | Stockmark 2 100B Instruct |
|---|---|---|
| Best for | multimodal apps and tool-calling agents | general production evaluation |
| Decision fit | Agents, Vision, and JSON / Tool use | Long context |
| Context window | — | 128K |
| Cheapest output | - | - |
| Provider routes | 1 tracked | 1 tracked |
| Shared benchmarks | 0 rows | 0 rows |
Decision tradeoffs
- MedGemma uniquely exposes Vision, Multimodal, and Function calling in local model data.
- Local decision data tags MedGemma for Agents, Vision, and JSON / Tool use.
- Stockmark 2 100B Instruct has the larger context window for long prompts, retrieval packs, or transcript analysis.
- Local decision data tags Stockmark 2 100B Instruct for Long context.
Monthly cost at traffic
Estimate token spend from the cheapest tracked input and output route or tier on this page.
MedGemma
Unavailable
No complete token price in local provider data
Stockmark 2 100B Instruct
Unavailable
No complete token price in local provider data
Cost delta unavailable until both models have sourced input and output token prices.
Switch friction
- No overlapping tracked provider route is sourced for MedGemma and Stockmark 2 100B Instruct; plan for SDK, billing, or endpoint changes.
- Check replacement coverage for Vision, Multimodal, and Function calling before moving production traffic.
- No overlapping tracked provider route is sourced for Stockmark 2 100B Instruct and MedGemma; plan for SDK, billing, or endpoint changes.
- MedGemma adds Vision, Multimodal, and Function calling in local capability data.
Specs
| Specification | ||
|---|---|---|
| Released | 2024-07-01 | 2025-06-01 |
| Context window | — | 128K |
| Parameters | 4B | 100B |
| Architecture | decoder only | decoder only |
| License | Proprietary | 1 |
| Knowledge cutoff | - | - |
Pricing and availability
| Pricing attribute | MedGemma | Stockmark 2 100B Instruct |
|---|---|---|
| Input price | - | - |
| Output price | - | - |
| Providers |
Pricing not yet sourced for either model.
Capabilities
| Capability | MedGemma | Stockmark 2 100B Instruct |
|---|---|---|
| Vision | Yes | No |
| Multimodal | Yes | No |
| Reasoning | No | No |
| Function calling | Yes | No |
| Tool use | Yes | No |
| Structured outputs | Yes | No |
| Code execution | No | No |
| IDE integration | No | No |
| Computer use | No | No |
| Parallel agents | No | No |
Benchmarks
No shared benchmark rows are currently sourced for this pair.
Deep dive
The capability footprint differs most on vision: MedGemma, multimodal input: MedGemma, function calling: MedGemma, tool use: MedGemma, and structured outputs: MedGemma. Both models share the core language-model surface, so the practical split is not just feature count. Use those differences to decide whether the page is about raw model quality, agentic coding support, multimodal ingestion, or predictable structured API behavior.
Pricing coverage is uneven: MedGemma has no token price sourced yet and Stockmark 2 100B Instruct has no token price sourced yet. Provider availability is 1 tracked routes versus 1. Treat unknown pricing as an integration gap, then verify the route you will actually call before estimating production spend.
Choose MedGemma when vision-heavy evaluation are central to the workload. Choose Stockmark 2 100B Instruct when provider fit are more important. For production, rerun your own prompts through the exact provider, region, and tool stack you plan to ship. This keeps the decision grounded in measurable tradeoffs instead of brand-level assumptions. It also helps separate model capability from provider packaging, which can change cost and latency. For teams standardizing a stack, that distinction is often the difference between a benchmark win and a reliable deployment.
FAQ
Is MedGemma or Stockmark 2 100B Instruct open source?
MedGemma is listed under Proprietary. Stockmark 2 100B Instruct is listed under 1. License labels affect whether you can self-host, redistribute weights, or rely only on hosted APIs, so confirm the upstream license before deployment.
Which is better for vision, MedGemma or Stockmark 2 100B Instruct?
MedGemma has the clearer documented vision signal in this comparison. If vision is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ. Use this as a quick comparison signal, then confirm the provider-specific limits before committing to production.
Which is better for multimodal input, MedGemma or Stockmark 2 100B Instruct?
MedGemma has the clearer documented multimodal input signal in this comparison. If multimodal input is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.
Which is better for function calling, MedGemma or Stockmark 2 100B Instruct?
MedGemma has the clearer documented function calling signal in this comparison. If function calling is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.
Which is better for tool use, MedGemma or Stockmark 2 100B Instruct?
MedGemma has the clearer documented tool use signal in this comparison. If tool use is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.
Where can I run MedGemma and Stockmark 2 100B Instruct?
MedGemma is available on GCP Vertex AI. Stockmark 2 100B Instruct is available on NVIDIA NIM. Provider coverage can affect latency, region availability, compliance posture, and fallback options. Use this as a quick comparison signal, then confirm the provider-specific limits before committing to production.
Continue comparing
Last reviewed: 2026-05-22. Data sourced from public model cards and provider documentation.