General reasoning and benchmark headroom.
UnavailableMagnum v4 72B is a mid-range-priced text-first model from anthracite-org with partial runtime data, compact context posture, and the clearest fit around long-context research.
Benchmark blend
Dev workflow signal
Compact
Mid-range tier
Magnum v4 72B currently reads as a mid-range text-first option with compact context and a partially published runtime profile.
Decision Strip
Core buy-side signals stay in one pass. The rest of the page expands only after intelligence, speed, context, and price are clear.
General reasoning and benchmark headroom.
UnavailableLatency data is partial.
UnavailableHow much prompt and task state can stay in view.
Limited$5.00 output / 1M
CompetitiveEditorial Profile
Positioning, tradeoffs, and fit are consolidated into one read instead of repeating the same story across separate cards.
This is a series of models designed to replicate the prose quality of the Claude 3 models, specifically Sonnet(https://openrouter.ai/anthropic/claude-3.5-sonnet) and Opus(https://openrouter.ai/anthropic/claude-3-opus). The model is fine-tuned on top of [Qwen2.5 72B](https://openrouter.ai/qwen/qwen-2.5-72b-instruct).
anthracite-org text-first profile
Long-context research with compact context and partially published runtime.
Balanced spend profile. Easier to justify in mixed production and exploration workloads.
The available source data suggests a balanced profile rather than one dominant edge.
Costs look manageable, but still deserve attention in always-on agents or batch jobs.
Latency data is incomplete, so interactive responsiveness is harder to rank confidently.
Current metadata points to a text-first profile rather than a broad multimodal one.
Context window is more comfortable for focused tasks than extremely long sessions.
Focused chat, retrieval-augmented flows, and narrower production tasks.
Benchmarks
Only benchmark categories with actual signal are shown. Secondary values stay as simple definitions instead of nested micro-cards.
Specs & Pricing
Specs stay neutral, pricing gets emphasis through values rather than extra containers. Raw provider internals remain in metadata at the end.
This model sits in a balanced spend range. It is easier to justify across both production and exploratory workflows.
Metadata
Verification details remain available, but the page no longer forces them ahead of the editorial read.