What compounds when you integrate.
The loop compounds
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.
Swap the model, keep the expertise
There's a new frontier model every few weeks. The routing intelligence doesn't reset when you switch — it persists across model swaps and travels with you across harnesses. You're building a layer that outlives whatever's underneath it.
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 HTASK 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
85
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.
Integration
Drop-in middleware.
Route tasks through Hokusai, execute them in your harness, then report the result back so the shared router can keep improving.
import { route } from '@hokusai/router'
const { model, reasoning } = await route({
task: userTask,
context: harnessContext,
})
const result = await models[model].run(userTask)
await route.reportOutcome(result) // mints tokens proportional to performance liftLearn how to contribute 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 |
What else the factory makes
The router is the first decision layer built on Hokusai. The same protocol applies to every model where shared, incentive-aligned learning beats siloed effort.
Tool-selection router
Same factory, same upside structure: which tool/MCP to call, learned from outcomes.
Learn moreMemory retrieval optimizer
A learned policy for what to surface from a user's context, contributors share in the lift.
Learn moreCode-review critic router
Which reviewer model catches which class of bug, improved by outcome data from real PRs.
Learn morePrompt-policy optimizer
A shared model for prompt strategies, owned by the engineers who improve it.
Learn more