AI's missing layers - owned by the engineers improving them

Our first model is a task router for multi-model coding harnesses. Integrate it and earn a stake every time your decisions improve it.

What you capture when you integrate.

Hokusai routes coding tasks for a per-decision fee. The fees back the token. You capture a position in that fee stream — plus a smarter router that lowers your inference costs along the way.

Backed by a real fee stream

Every routing call through Hokusai pays a per-decision fee in USDC. Those fees flow into the router's bonding curve and back the token's redemption value. Your stake is a position in real network revenue, not in a performance metric.

A position in the router

Every meaningful improvement your outcome data produces mints HTASK tokens to you. The token is a position in the router's fee stream — held as ownership, or redeemed for USDC anytime.

Lower inference cost

A smarter router picks the right model for each task. You spend less on inference before counting any token rewards.

Configurable value share

Decide at integration whether to keep the token flow as revenue, pass it through to your users as an ownership feature, or split the two. Configurable later, not just at setup.

Inside a routing decision

Read the protocol →

Incoming task

Refactor auth middleware to support scoped API keys
high priority

Refactor the existing auth middleware so API keys can be restricted to specific scopes and routes. Requirements: - Keep the current middleware entrypoint stable for integrators. - Enforce scope checks before request handlers run. - Preserve existing admin flows while tightening least-privilege defaults. - Add tests covering missing scope, partial scope, and valid scope paths. - Document any new assumptions in code comments near the policy boundary.

auth
backend
middleware
api-keys

Task packet

Summarize & anonymize task

Refactor auth middleware to support scoped API keys

Language: typescript
Domain: backend
Task type: refactor
Complexity: 6/10
Risk: medium
Budget: $25

Available model families

Claude
GPT
Gemini
OpenAI o-series

Choice Layer

Find the most similar tasks that succeeded within the budget constraints

Historical outcomes with similar task packets are scored against the current budget and evaluation envelope, then narrowed to the route most likely to hold up end to end.

Output

Planner

claude-opus-4-7

Strong at shaping the migration plan and isolating policy boundaries.

Available for fallback

gpt-5.4
claude-sonnet-4-6

Coder

gpt-5.4

Best fit for the implementation pass and test repair inside budget.

Available for fallback

claude-sonnet-4-6
gemini-2.5-pro

Reviewer

claude-sonnet-4-6

Good balance for regression review and policy edge-case coverage.

Available for fallback

gpt-5.4
o4-mini

Evaluation

Evaluate the recommendations

How the run scored against the eval rubric.

Total cost

$18.42

Planner score

9.2 / 10

Coder score

8.7 / 10

Reviewer score

9.5 / 10

Wall clock

6m 52s

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 lift
Learn how to contribute

Where does your routing data go today?

 Lab-owned auto-routingHokusai
Who pays for routing decisionsThe lab keeps it as gross marginIntegrators pay; fees back the contributor token.
Who captures the optimization signalThe labYou and the contributors
Who keeps the inference cost savingsThe lab keeps marginYou
What you build over timeNothing transferableA token position in the router
Portability across harnessesLocked inTake your position with you
AuditabilityOpaqueOn-chain attribution
At ~10,000 coding tasks/week, the optimization value lab-side routers capture is roughly $10k/month (illustrative). With Hokusai, that value flows to integrators and contributors.