Claude Mythos 5.1 vs Granite Embedding 30m English
At a Glance
| Compare | Claude Mythos 5.1Anthropic | |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $10.00Anthropic ↗ · Sep 2, 2026 | Not reported |
| Output priceFrom · USD / 1M tokens | $50.00Anthropic ↗ · Sep 2, 2026 | Not reported |
| Context windowMaximum documented tokens | 1,000K | 1K |
| Model facts checked | Sep 2, 2026View model evidence → | Aug 28, 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 →
Available Benchmarks
Side-by-Side Facts
| Field | Claude Mythos 5.1 | granite-embedding-30m-english |
|---|---|---|
| Developer | Anthropic | IBM |
| Family | Claude 5 1 | Granite Embedding 30m English |
| Model | Claude Mythos 5.1 | granite-embedding-30m-english |
| Version | Claude Mythos 5.1 | granite-embedding-30m-english |
| Lifecycle | active | active |
| Released | 2026-09-01 | 2025-08-29 |
| Knowledge cutoff | 2026-06-01 | Unknown |
| Input modalities | Text, Image | Text |
| Output modalities | Text | Embedding |
| Context window | 1,000K | 1K |
| Total parameters | Unknown | 30.3M |
| Active parameters | Unknown | Unknown |
| License | Unknown | apache-2.0 |
| Open weights | No | Yes |
| API available | Yes | Yes |
| Self-hostable | No | Yes |
| Provider access | Anthropic (Project Glasswing) | Hugging Face (Standard) |
| Capabilities | chat, generation, reasoning, tools | embeddings |
Claude Mythos 5.1 Capabilities
Granite Embedding 30m English Capabilities
Primary Evidence
Sources and Freshness
Questions
Claude Mythos 5.1 vs Granite Embedding 30m English FAQs
Is Claude Mythos 5.1 or Granite Embedding 30m English better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Claude Mythos 5.1 and Granite Embedding 30m English, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Claude Mythos 5.1 or Granite Embedding 30m English?+
Only Claude Mythos 5.1 has a directly sourced input price: $10.00 per million tokens. Only Claude Mythos 5.1 has a directly sourced output price: $50.00 per million tokens.
Which has a larger context window, Claude Mythos 5.1 or Granite Embedding 30m English?+
Claude Mythos 5.1 has the larger sourced context window. Claude Mythos 5.1 supports 1,000K and Granite Embedding 30m English supports 1K.
Which performs better in benchmarks, Claude Mythos 5.1 or Granite Embedding 30m English?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Claude Mythos 5.1 or Granite Embedding 30m English be self-hosted?+
Granite Embedding 30m English is the only model in this pair currently marked as self-hostable. Claude Mythos 5.1 is not marked open weight; Granite Embedding 30m English is open weight.
Can Claude Mythos 5.1 and Granite Embedding 30m English understand images?+
Claude Mythos 5.1 is documented with image input; Granite Embedding 30m English is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Claude Mythos 5.1 or Granite Embedding 30m English?+
Neither has a larger sourced maximum output. Claude Mythos 5.1 is 128K and Granite Embedding 30m English is —.
Do Claude Mythos 5.1 and Granite Embedding 30m English support reasoning and tool use?+
Claude Mythos 5.1: reasoning, tool calling, and image input. Granite Embedding 30m English: none of these features are definitively sourced. Feature support does not establish relative quality.
Which is available from more inference providers, Claude Mythos 5.1 or Granite Embedding 30m English?+
Claude Mythos 5.1 has 1 sourced provider route; Granite Embedding 30m English has 1, a tie.
Which offers better value, Claude Mythos 5.1 or Granite Embedding 30m English?+
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.