Save up to 4x
on input & output tokens
Choose the model that matches the job — not a one-size-fits-all bill. Nova for the hardest work in the family, Magma when flagship depth is enough, Blaze for everyday production agents, Ember for high-volume long-context work. Same platform. Clear price points. Built for IDE, Cloud, CLI, and API.
Flagship reasoning for work where getting it wrong is expensive.
Nova is 4RGED’s highest-capability model. It is built for the hardest plans, the sharpest trade-offs, and multi-step agent runs where Magma is no longer enough.
Use Nova when the model must hold a large design space in mind — system boundaries, migration risks, policy constraints — and still produce a plan you can execute.
It excels at architecture reviews, complex refactors, and agent loops that call tools across many files or services before committing to an answer.
If Magma keeps missing edge cases or collapsing plans too early, Nova is the upgrade inside the same 4RGED family. Stay on Magma, Blaze, or Ember when that depth is not required.
What it does well
Frontier-depth reasoning
Handles ambiguous requirements, conflicting constraints, and multi-hop decisions without shortcutting to a shallow answer.
Architecture & planning
Breaks large changes into sequenced steps, surfaces risks early, and keeps system-wide context across long sessions.
Multi-step agent execution
Stays coherent across tool calls, retries, and verification loops — built for agents that must finish the job, not just draft a reply.
Choose this when
The hardest reasoning, architecture decisions, and critical agent workloads.
Analytics
Customer use cases
System design & architecture reviews
Evaluate trade-offs across services, data stores, and rollout plans with explicit risks and alternatives.
Long-horizon coding agents
Drive agents that research, edit, test, and revise across a large codebase before proposing a merge-ready change.
Hard refactors & migrations
Plan and execute migrations where order-of-operations and compatibility matter as much as the code itself.
Policy, security & correctness review
Pressure-test PRs and agent output for subtle failures, unsafe patterns, and compliance gaps.
Deep reasoning for work where getting it wrong is expensive.
Magma sits just under Nova. It is built for long-horizon plans, hard trade-offs, and multi-step agent runs where depth matters more than raw speed — without Nova’s unit price on every request.
Use Magma when the model must hold a large design space in mind — system boundaries, migration risks, policy constraints — and still produce a plan you can execute.
It excels at architecture reviews, complex refactors, and agent loops that call tools across many files or services before committing to an answer.
If a cheaper model keeps missing edge cases or collapsing plans too early, Magma is the upgrade. Move up to Nova only when Magma still is not enough.
What it does well
Frontier-depth reasoning
Handles ambiguous requirements, conflicting constraints, and multi-hop decisions without shortcutting to a shallow answer.
Architecture & planning
Breaks large changes into sequenced steps, surfaces risks early, and keeps system-wide context across long sessions.
Multi-step agent execution
Stays coherent across tool calls, retries, and verification loops — built for agents that must finish the job, not just draft a reply.
Choose this when
Complex reasoning, architecture decisions, and critical agent workloads.
Analytics
Customer use cases
System design & architecture reviews
Evaluate trade-offs across services, data stores, and rollout plans with explicit risks and alternatives.
Long-horizon coding agents
Drive agents that research, edit, test, and revise across a large codebase before proposing a merge-ready change.
Hard refactors & migrations
Plan and execute migrations where order-of-operations and compatibility matter as much as the code itself.
Policy, security & correctness review
Pressure-test PRs and agent output for subtle failures, unsafe patterns, and compliance gaps.
The production default — strong coding agents at a lower unit cost.
Blaze is the workhorse of the 4RGED family: excellent coding and agent quality with enough headroom for real production systems — without Magma pricing on every request.
Most teams should start here. Blaze covers pair-programming in the IDE, Cloud parallel runs, CI fixes, and CLI automation with reliable reasoning and fast turnaround.
It balances depth and cost: strong enough for production agent orchestration, efficient enough to run continuously across a team or fleet.
Move up to Magma when Blaze under-delivers on hard planning, and to Nova only when Magma still is not enough. Move down to Ember when the job is high-volume summarization or routing.
What it does well
Production coding quality
Writes, edits, and explains code with strong repo awareness — tuned for IDE pair-programming and review loops.
Reliable under load
Built for everyday production traffic: consistent behavior across many sessions, orgs, and agent types.
Agentic orchestration
Coordinates tools, tests, and multi-agent workflows without needing flagship pricing on every turn.
Choose this when
Production workloads, coding agents, and day-to-day orchestration.
Analytics
Customer use cases
IDE pair-programming agents
Inline edits, explanations, and multi-file changes while an engineer stays in flow.
Cloud parallel agent fleets
Spin up many agents on tickets, PRs, or migrations without flagship cost on each run.
CI, CLI & automation
Fix failing checks, generate patches, and drive scripted workflows from the terminal or pipelines.
Team default for new projects
Standardize on one model so policy, prompts, and evals stay simple across the org.
Maximum context and throughput for everyday high-volume work.
Ember is optimized for scale: the largest context window in the family at the lowest price — ideal when you need to read a lot, respond quickly, and run many jobs.
Reach for Ember when the bottleneck is volume or document size — chat assistants, summarization, classification, routing, and ingestion pipelines — not deep architecture planning.
Its 2M context window lets you keep long threads, large PDFs, or multi-file dumps in a single pass instead of brittle chunking.
Pair Ember with Blaze, Magma, or Nova in a router: Ember handles the high-volume front door; escalate harder tasks only when needed.
What it does well
High-throughput responses
Built for queues and interactive chat where latency and cost per request dominate.
Large document & dataset intake
Ingest long docs, transcripts, and dumps in fewer passes — less glue code, fewer missed sections.
Efficient long-context processing
2M input and output context for jobs that would otherwise require aggressive truncation.
Choose this when
Everyday chat, summaries, triage, and high-volume long-context jobs.
Analytics
Customer use cases
Customer & internal chat assistants
Fast answers across long histories without burning Magma or Blaze budget on every message.
Summaries & briefings
Collapse tickets, meetings, and docs into actionable notes at high volume.
Classification & triage pipelines
Label, route, and prioritize incoming work before a deeper model gets involved.
Large-context ingestion
Pull big files and datasets into agents for search, extract, and transform workflows.
USD per 1M tokens
USD per 1M tokens
03 Efficiency & scale
on input & output tokens
with optimized inference
Secure. Scalable. Reliable.
APIs, Agents & real-world scale.