MedGemma 4B
llmtr/medgemma-4bمن llmtr · أُصدِر 2026-04-26
⚠ هذا نموذج مُحسَّن من المجتمع أو مشتق — وليس إصدارًا رسميًا من المزود.
Prices in USD per 1M tokens. Unknown means the provider does not publish per-token pricing.
القدرات
Model fit scores
0–100 · higher is betterThese scores reward declared capabilities, context size, price and provider availability — they are not benchmark results. Use them as a directional signal alongside your own evaluation.
Coding1
- Tool calling0/40
- Structured output0/20
- Reasoning0/10
- Context window (100K → 1M)0/20
- Provider availability1/10
Agents1
- Tool calling0/35
- Structured output0/25
- Reasoning0/15
- Output token limit0/15
- Provider availability1/10
JSON / structured output14
- Structured output / JSON mode0/50
- Tool calling0/20
- Temperature control10/10
- Price-friendly for high-volume4/20
Cost efficiency40
- Headline price (log-scaled)40/95
- Has prompt-cache pricing0/5
Long context0
- Context ≥ 100K0/100
Vision61
- Accepts image input50/50
- Context window (10K → 1M)0/30
- Has published price10/10
- Provider availability1/10
Production-readiness43
- Number of independent providers5/40
- Has published per-token price20/20
- Context window ≥ 8K8/15
- No data inconsistencies across providers10/10
- Official model (not derivative)0/15
Cost Efficiency Index
Open full calculator →Estimated cost using the recommended provider's headline rate. Each scenario fixes average input/output tokens — the assumptions are shown in the third column.
| Scenario | Cost | Assumption |
|---|---|---|
RAG answer per 1,000 RAG answers | $17.50 $0.02 per request | 5K input tokens (query + 4 retrieved chunks of ~1K each) and a 500-token answer. Typical SaaS knowledge-base bot. |
Support ticket triage per 10,000 tickets | $35.00 < $0.01 per request | 1K input tokens (ticket body + system prompt) and a 100-token JSON classification reply. High-volume customer support. |
Data extraction per 1,000 documents | $8.50 < $0.01 per request | 2K input tokens (a single document page) and a 500-token JSON extraction. ETL / invoice / form pipelines. |
Code review per 1,000 PRs | $29.00 $0.03 per request | 8K input tokens (diff + surrounding files) and a 1K-token review comment. PR-bot workloads. |
Agent step per 1,000 steps | $39.00 $0.04 per request | 12K input tokens (long-running tool history) and a 600-token tool-call decision. Cost per agent step. |
تفاصيل التسعير
السعر المُوصى به من llmtr · medgemma-4b
متاح لدى 1 مزود
| المزود | معرف نموذج المزود | إدخال / 1M | إخراج / 1M | السياق | تاريخ الإصدار |
|---|---|---|---|---|---|
| LLMTR llmtr | medgemma-4b | $3.00 | $5.00 | 8K | 2026-04-26 |
Frequently asked questions
How much does MedGemma 4B cost?
MedGemma 4B costs $3.00 per 1M input tokens and $5.00 per 1M output tokens, sourced from llmtr. Cache reads, audio tokens and >200K-context tiers (where applicable) are listed in the Pricing detail block above.
What is the context window of MedGemma 4B?
MedGemma 4B has a context window of 8K tokens, with a max output of 4K tokens per reply. This is the total combined size of prompt + completion.
Does MedGemma 4B support tool calling?
No. MedGemma 4B does not support tool calling (function calling). If your workflow requires it, look at the /capabilities/tool-calling list for alternatives.
Does MedGemma 4B support structured output / JSON mode?
Support for structured output / JSON-schema-constrained decoding is not reported for MedGemma 4B in our data source. Verify with llmtr's official documentation before relying on it in production.
Can MedGemma 4B accept image input?
Yes. MedGemma 4B accepts both text and image input. Vision pricing per image is usually billed on top of the regular token rate — check llmtr's docs for the exact rule.
Is MedGemma 4B open-weight?
Yes. MedGemma 4B's weights are publicly available, so you can self-host or fine-tune. Note that open weights ≠ open source — the training data and code are typically not released.
What are the best alternatives to MedGemma 4B?
If MedGemma 4B doesn't fit, consider Magibu 11B v8, Trendyol 7B, Sincap. Each one targets the same use case — see the Related links below for direct head-to-head pages.
Where does this data come from?
All numbers are normalised into a single canonical model record and reconciled with each provider's official documentation. We re-pull daily and write any changes (price, context, capability) to the /changelog page.
Explore more
More llmtr models
- Magibu 11B v8Unknown pricing
- Trendyol 7BUnknown pricing
- SincapUnknown pricing
Capability lists this model is in
آخر تحديث:
Pricing and capabilities are refreshed daily and reconciled against each provider's official documentation. Always verify critical production decisions with the provider directly.