Route among your models.Learn from outcomes.

A task router for multi-model coding harnesses. You provide the candidate model pool, Hokusai recommends one, and reported outcomes improve the shared router.

What compounds when you integrate.

Steadily improving loop

Every outcome you report trains the shared model. The router you integrate today is the worst one you'll ever run. It gets sharper using results from every harness on the protocol, not just yours, and you didn't have to build it.

Route across your real model pool

Hokusai only routes among models you explicitly make available. Add the models your harness can actually run, report outcomes, and keep improving the layer that chooses between them.

Lower inference cost

The router picks the right model for each task instead of sending everything to the biggest one. You spend less on inference before a single token is counted.

A stake in what you improve

Outcome data that measurably improves the router mints HROUT to you — a position in its per-decision fee stream, held as ownership or redeemed for USDC anytime. Keep it as revenue, pass it through to your users, or split it.

Coding / Multi-Model Routing

Coding Task Router

Hokusai's first router corpus comes from real autonomous coding evals, not synthetic routing examples.

696

Deduplicated router-training records

209

Challenge-mode routing examples

Head-to-head model comparisons

88%

Migration, feature, and bugfix work

The data spans migrations, features, bug fixes, infra, tests, refactors, and docs across TypeScript, JavaScript, Python, Bash, and mixed-language repos. This provides a decent starting point for learning routing behavior while leaving clear room to expand coverage across more repositories, languages, and task families.

Learn more about how the choice layer works

Integration

Bring Hokusai to your existing workflow.

Use Hokusai from coding assistants, agent harnesses, backend services, or direct API calls. Pick the path that matches your workflow, then route tasks and report outcomes.

Choose an integration point

Start from the workflow you already use: a coding assistant, an agent harness, application code, or a direct API call.

Route against your model pool

Pass only the candidate models your environment can actually run. Hokusai recommends one; your system still executes the task.

Report outcomes

Send coarse success, cost, latency, and token signals back to the protocol so the shared router improves.

Claude CodeCodexWavemillTypeScriptPythonREST API

See all integration paths

Where does your routing data go today?

	Lab-owned auto-routing	Hokusai
Who pays for routing decisions	The lab keeps it as gross margin	Integrators pay; fees back the contributor token.
Who captures the optimization signal	The lab	You and the contributors
Who keeps the inference cost savings	The lab keeps margin	You
What you build over time	Nothing transferable	A token position in the router
Portability across harnesses	Locked in	Take your position with you
Auditability	Opaque	On-chain attribution

Future decision layers

The shipped SDK surface today is model routing for coding tasks. These are future decision-layer candidates, not implemented @hokusai/router APIs.