Fugu Ultra vs Hy3

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 Hy3, side by side, on 2 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.

Hy3 · Wired into the Agent OS as the 'Hy3 Coder' tab (chat + live preview + workspace) via OpenRouter. Bench built one-shot on the same prompts as the field; weak builds iterated by Hy3 itself (the model fixes its own builds).

Where Fugu Ultra beat Hy3

The tasks where I gave Fugu Ultra a higher 0–10 score on the same prompt — with the actual commentary from my source guides.

Where Hy3 beat Fugu Ultra

The tasks where I gave Hy3 a higher 0–10 score on the same prompt — with the actual commentary from my source guides.

Strengths & weaknesses I logged

Pricing & context — the spec sheet

The verdict — which should you pick?

Across 2 scored shared tasks, Fugu Ultra averaged 7.00/10, beating Hy3's 6.35/10 by 0.65 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 Hy3 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, cost-sensitive coding + frontend design where open weights matter → Hy3. That's the same setup I run for the 3,600+ founders inside the AI Profit Boardroom.

FAQ — Fugu Ultra vs Hy3

Which is better, Fugu Ultra or Hy3?

On Goldie Bench, Fugu Ultra averages 7.00/10 across the shared tasks, with 6 gold, 6 silver, 5 bronze overall. Hy3 averages 6.35/10, with 0 gold, 1 silver, 0 bronze. It's a curated tie on the head-to-head.

How much does Fugu Ultra cost vs Hy3?

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. Hy3: Tencent Hunyuan 3 — open-weights under Apache-2.0, so free to self-host. On OpenRouter it is one of the cheapest capable coders: ~$0.14/M in, $0.58/M out (1 RMB / 4 RMB). Upstream can be slow (30-90s to first token), but per-token cost is negligible.

What's the context window for Fugu Ultra vs Hy3?

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. Hy3 has a 262,144-token context window. Open weights (Apache-2.0) on HuggingFace / ModelScope / GitHub; benched here via OpenRouter. context window.

When should I pick Fugu Ultra over Hy3?

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 Hy3 over Fugu Ultra?

Pick Hy3 for: Cost-sensitive coding + frontend design where open weights matter; Self-hosters who want an Apache-2.0 model they fully own; Anyone wiring a cheap capable coder into a live build panel (Agent OS Hy3 Coder tab). The trade-off is the weaknesses we logged on the bench: Slow upstream on OpenRouter (30-90s per build) — fine for one-shots, sluggish for tight loops; One-shot game builds can under-render (flat raycaster walls, unlit 3D) without an iterate pass.

How does Goldie Bench score Fugu Ultra vs Hy3?

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:

Full model pages: Fugu Ultra · Hy3 · back to the leaderboard