IBM: Granite 4.1 8B
Decision snapshot from the global rankings; composite scoring matches the on-site model board.
Data updated:
Model
1 verified sources
Aggregator quote only — no official sync yet
Next steps on AI Hippo
Open weights snapshot
ibm-granite/granite-4.1-8b
Task text-generation
- Downloads
- 601.9k
- Likes
- 204
- Parameters
- 0B
About this model
IBM: Granite 4.1 8B ranks #37 on our global model leaderboard. It is listed as a LLM with 131k ctx and a typical snapshot price around $0.07 per 1M tokens. Use Compare for side-by-side picks or the Token hub for verified multi-provider pricing from the same snapshot.
You can also explore more models from Ibm Granite , and browse more options from 🇺🇸 United States .
Capabilities & specs
- Modality
- text->text
- Input modalities
- text
- Supported API parameters
- frequency_penalty, logprobs, max_tokens, presence_penalty, repetition_penalty, response_format, seed, stop, structured_outputs, temperature, tool_choice, tools, top_k, top_logprobs, top_p
Catalog description: Granite 4.1 8B is a dense, decoder-only 8-billion-parameter language model from IBM, part of the Granite 4.1 family. It supports a 131K-token context window and is designed for enterprise tasks...
Token pricing by provider
Compare per-provider token prices for this model across available platforms.
| Provider | Input / 1M tokens | Output / 1M tokens | Latency | Status |
|---|---|---|---|---|
| OpenRouter | $0.05 | $0.10 | — | Verified · 2026-07-10 |
Provider prices are sourced from the token comparison dataset and may change between snapshots.
Alternative picks
-
Qwen: Qwen3 Coder 480B A35B (free)
Compare now -
DeepSeek: DeepSeek V4 Flash
Compare now -
Z.ai: GLM 5.2
Compare now
Pick one or two more models on global rankings and use Compare to view them side by side.
FAQ
Why is the official price missing?
Official rows require a verified direct vendor or cloud API price. When only aggregators list a model, the Official column shows — and verified aggregator quotes appear in the token table.
How is context different from max output tokens?
Context window is how much input the model can accept in a single request. Max output tokens is the per-response generation cap from the primary listing—often much smaller than the context window.
Where do multi-provider prices come from?
Prices are crawled or synced from token providers (OpenRouter, Groq, Together, and others) and merged into the infrastructure comparison dataset. Verified rows show a fetch date in the status column.
Data source & methodology
- Source
- OpenRouter catalog, verified vendor crawls, and Hugging Face hub snapshots.
- Metrics
- Context window, blended 1M-token price, max output tokens, and capability fields from the OpenRouter models API.
- Update cadence
- Daily pipeline refresh; provider prices may change between snapshots.
- Fetched at
- 2026-07-10
- Method
- Composite rank uses on-site context × price weighting (not LMSYS Arena ELO).