
Fugu Ultra vs Fugu Mini
Sakana's multi-agent answer to Fusion — frontier ensemble without single-vendor risk. vs Fugu's fast mini variant — single model, no panel, ~3 min per build.
Head-to-head verdict: Fugu Ultra wins 1–0.
What I tested — same prompt, two models
I run the same fixed prompt set through every new model the day it drops — same string, one shot, single HTML file out — and I score the result 0–10 on whether it ran, how close it hit the brief, and how good it looked. Below is what came out when I gave the exact same prompts to Fugu Ultra and Fugu Mini, side by side, on 4 shared tasks inside the Agent Operating System.
Both models were given identical prompts inside the Agent Operating System — no help, no iteration, no "best of N" tricks. I run each prompt once, save the HTML file the model produces, and score it 0–10 on whether it ran, how close it hit the brief, and how good it looked. The scoring is mine. The verdicts below are pulled from my source comparison guides at agentos.guide where I publish every score and the reasoning behind it.
Fugu Ultra · Dispatched from Agent OS as the panel-ensemble alternative to OpenRouter Fusion. Bench scored by Claude judge against the same 42 prompts as every other model.
Fugu Mini · Dispatched from Agent OS as the fast Sakana lane. Bench scored by Claude judge against the same 42 prompts.
Side-by-side on 27 shared tasks
Click any cell to play that model's actual one-shot attempt. Medals are derived from my 0–10 scores per task (highest = 🥇, second = 🥈, third = 🥉).
Where Fugu Ultra beat Fugu Mini
The tasks where I gave Fugu Ultra a higher 0–10 score on the same prompt — with the actual commentary from my source guides.
What I saw: TRUNCATED — Fugu hit my 16K max_tokens ceiling mid-particle-spawn function. The 28KB it shipped has rich setup (HUD, lane geometry, obstacle/coin spawning, particle pool) but NO animation loop and NO input handlers, plus an unclosed <script> tag. Loads to a static scene; doesn't …
Strengths & weaknesses I logged
Fugu Ultra
Strengths
- SWE Bench Pro 73.7 · GPQA-D 95.5 · MRCRv2 93.6 — Sakana's published frontier-tier benchmark scores
- Vendor-agnostic ensemble — opt out of specific providers for compliance / export-control
- OpenAI-compatible API at api.sakana.ai — drop-in for existing tooling
Trade-offs
- Panel orchestration adds latency — even a 'pong' burns ~2k orchestration tokens
- Newer than Fusion; less community calibration on long-tail prompts
Fugu Mini
Strengths
- Zero panel orchestration — much lower latency than Ultra
- Same Sakana subscription, no extra cost
- Doesn't time out on heavy game/3D prompts where Ultra stalls
Trade-offs
- Single model only — no ensemble verdict
- Newer than Ultra — less calibration / verification
Pricing & context — the spec sheet
| Spec | Fugu Ultra | Fugu Mini |
|---|---|---|
| Vendor | Sakana AI | Sakana AI |
| Context window | 272,000 tokens with the standard rate. Calls exceeding 272K context are billed at the higher 'long-context' rates. | Single-model variant of Sakana's Fugu — no panel orchestration. Same API endpoint, much faster per call. |
| Price | $5 / 1M input · $30 / 1M output (Fugu Ultra) | Same Sakana subscription pool as Fugu Ultra |
| Pricing detail | Sakana's multi-agent orchestration: a single API call internally dispatches to multiple frontier models and synthesises the answer. Subscription plans run $20-$200/mo (Standard / Pro / Max); PAYG is $5/M input + $30/M output for Fugu Ultra. Direct competitor to OpenRouter Fusion's panel approach. | The non-Ultra `fugu` model on Sakana's API. Sakana describes it as 'Fast mini model optimized for low latency yet high quality responses.' Crucially: zero orchestration tokens per call (vs Ultra's panel of thousands). Returns in ~3 min instead of 6-15 min and doesn't time out on heavy prompts. |
| Release | 2026-06-15 | 2026-06-15 |
| Bench coverage | 5/5 scored · avg 7.60/10 | 2/26 scored · avg 5.50/10 |
The verdict — which should you pick?
Across 1 scored shared tasks, Fugu Ultra averaged 3.50/10, beating Fugu Mini's 3.00/10 by 0.50 points. Pick Fugu Ultra when the build has to ship on the first prompt and you can afford the trade-offs in the comparison below.
If you only run one of these inside your stack, the head-to-head average above is the call. If you can run both, my honest play is to wire Fugu Ultra and Fugu Mini both into the Agent Operating System and dispatch each from the kanban by task type — teams that want fusion-class quality but need a different vendor risk profile → Fugu Ultra, agent loops where latency matters more than panel consensus → Fugu Mini. That's the same setup I run for the 3,600+ founders inside the AI Profit Boardroom.
FAQ — Fugu Ultra vs Fugu Mini
Which is better, Fugu Ultra or Fugu Mini?
On Goldie Bench, Fugu Ultra averages 3.50/10 across the shared tasks, with 3 gold, 1 silver, 0 bronze overall. Fugu Mini averages 3.00/10, with 0 gold, 0 silver, 0 bronze. Fugu Ultra wins the head-to-head 1–0.
How much does Fugu Ultra cost vs Fugu Mini?
Fugu Ultra: Sakana's multi-agent orchestration: a single API call internally dispatches to multiple frontier models and synthesises the answer. Subscription plans run $20-$200/mo (Standard / Pro / Max); PAYG is $5/M input + $30/M output for Fugu Ultra. Direct competitor to OpenRouter Fusion's panel approach. Fugu Mini: The non-Ultra `fugu` model on Sakana's API. Sakana describes it as 'Fast mini model optimized for low latency yet high quality responses.' Crucially: zero orchestration tokens per call (vs Ultra's panel of thousands). Returns in ~3 min instead of 6-15 min and doesn't time out on heavy prompts.
What's the context window for Fugu Ultra vs Fugu Mini?
Fugu Ultra has a 272,000 tokens with the standard rate. Calls exceeding 272K context are billed at the higher 'long-context' rates. context window. Fugu Mini has a Single-model variant of Sakana's Fugu — no panel orchestration. Same API endpoint, much faster per call. context window.
When should I pick Fugu Ultra over Fugu Mini?
Pick Fugu Ultra for: Teams that want Fusion-class quality but need a different vendor risk profile; Operators avoiding export-controlled providers (Sakana emphasises this in their pitch); Deep-research workflows where ensemble verdicts beat single-model answers. The trade-off is the weaknesses we logged on the bench: Panel orchestration adds latency — even a 'pong' burns ~2k orchestration tokens; Newer than Fusion; less community calibration on long-tail prompts.
When should I pick Fugu Mini over Fugu Ultra?
Pick Fugu Mini for: Agent loops where latency matters more than panel consensus; Quick first-drafts you'll refine downstream; Filling out a bench when Ultra is timing out. The trade-off is the weaknesses we logged on the bench: Single model only — no ensemble verdict; Newer than Ultra — less calibration / verification.
How does Goldie Bench score Fugu Ultra vs Fugu Mini?
Every demo on this page was built by Julian Goldie inside the Agent Operating System — same fixed prompt for both models, one shot, single HTML file out. Each result gets a 0–10 score on whether it ran, how close it hit the brief, and how good it looked. The highest score on each task gets gold; second gets silver; third gets bronze. See methodology for full provenance.
Related comparisons
Other head-to-heads using the same scoring system:
Fugu Ultra vs Fusion Fugu Mini vs Fusion Fugu Ultra vs Opus 4.8 Fugu Mini vs Opus 4.8 Fugu Ultra vs GLM-5.2 Fugu Mini vs GLM-5.2 Fugu Ultra vs Grok Fugu Mini vs GrokFull model pages: Fugu Ultra · Fugu Mini · back to the leaderboard
Run this stack yourself.
Every demo on this bench was built inside the Agent Operating System — one prompt, one shot, single HTML file out. The Agent OS, the prompts, the templates, the weekly walkthroughs and 3,600+ founders shipping with it every day all live inside the AI Profit Boardroom.

























