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

Inkling · Benched on GoldieBench one-shot through Tinker's OpenAI-compatible endpoint at medium reasoning effort, then headless-playtested on the same rubric as the whole field. In the Agent OS it's wired into the opencode tab on your own Tinker key — the Ink Machine.

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 Inkling beat Hy3

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

Where Hy3 beat Inkling

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 7 scored shared tasks, Hy3 averaged 6.76/10, beating Inkling's 5.87/10 by 0.89 points. Pick Hy3 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 Inkling and Hy3 both into the Agent Operating System and dispatch each from the kanban by task type — owning a frontier model instead of renting one — on your own key, pennies per build → Inkling, cost-sensitive coding + frontend design where open weights matter → Hy3. That's the same setup I run for the 4,000+ founders inside the AI Profit Boardroom.

FAQ — Inkling vs Hy3

Which is better, Inkling or Hy3?

On Goldie Bench, Inkling averages 5.87/10 across the shared tasks, with 0 gold, 3 silver, 1 bronze overall. Hy3 averages 6.76/10, with 0 gold, 0 silver, 0 bronze. Hy3 wins the head-to-head 5–1.

How much does Inkling cost vs Hy3?

Inkling: Inkling is open-weights — a 975B-parameter (41B active) Mixture-of-Experts model whose full weights are public on Hugging Face. You run it on your own key through Tinker's OpenAI-compatible endpoint (usage-based, ~$0.33/M sampling, 50% off at launch), or via Together / Fireworks / Modal / Databricks / Baseten. Benched here one-shot at medium reasoning effort via Tinker. 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 Inkling vs Hy3?

Inkling has a 1,000,000 tokens 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 Inkling over Hy3?

Pick Inkling for: Owning a frontier model instead of renting one — on your own key, pennies per build; Generative visuals, data-viz and single-file web builds you want one-shot; A customizable open base you can fine-tune on Tinker for your own domain. The trade-off is the weaknesses we logged on the bench: One-shot 3D games are weak — three.js dungeons/racers render a title screen but no playable scene, like most open models (crypt 2.5); Physics and particle sims are hit-or-miss — black-hole, plasma and cloth one-shots often render dark or static (2.3–3.5); Not the strongest overall — the closed frontier (Fable 5) still tops the raw benchmarks; Inkling trades peak for ownership.

When should I pick Hy3 over Inkling?

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 Inkling 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: Inkling · Hy3 · back to the leaderboard