Settled batch demand signals

A proof surface built from completed BatchRouter batches. It shows which workflow products, models, providers, and operations are carrying real settled demand through the routing marketplace.

Workflow product rankings

See which packaged workflows are carrying real settled demand.

Loading demand signals...

Model leaderboard

See which models actually carry live demand once settled workflow traffic starts landing.

Loading demand signals...

Operation share

See whether the current traffic mix is mainly response generation or embedding work.

No operation data yet.

Once work settles, the operation mix will show up here.

How this proof surface works

This is product usage telemetry for public decision-making, not a synthetic benchmark.

Source: Settled usage ledger entries joined to completed batch metadata.
Ranked by: Token share when tokens exist, falling back to request share when needed.
When to use it: After recurring workflows are already shipping and you want public proof of real demand.
Why it matters: Customers can see which workflow products and models carry workload, while providers and operators can spot where demand is concentrating.
Edge story: Edge supply networks can point to real routed demand instead of just catalog presence.