routerflow.artthe marketour probecomparemethodologyprobestaxonomyprober methodapi/v12026-11-10

Market tab: design brief

Status: built 2026-09-19, all three phases. Code: index.html (markup, charts) and site/market-ui.js (rail, tables, detail, pins, URL state).

Objective: restructure the market tab around the inference supply chain (apps, routers, models, providers, hardware, plus public and private) so a reader can find a layer, read who holds the flow there, and compare its members, without reading prose.

1. What the research says

Three reviews: nine crypto market-structure sites, ten AI and internet measurement sites, and the UX literature. Claims marked (2nd) come from search results or docs because the site blocked fetching.

Patterns that recur on the sites that work

#PatternSeen onUse here
1Flow overview as the spine, then one view per layerorderflow.art, Cloudflare Radar (2nd)Overview, then sections 1 to 6
2One template reused for every entity typeArtificial Analysis, L2BEAT, Radar (2nd)Identical section anatomy
3One wide sortable table per layer, grouped column headers, fixed column grammarL2BEAT, Artificial Analysis, DefiLlama (2nd)The side-by-side table
4Data quality is a column and a grouping, never a footnoteL2BEAT stages, Epoch "administered by us""Publishes" column, source badge
5Unit restated in every subtitle; shares-only sources say soOpenRouter rankings, Vercel leaderboardsUnit in every header
6Source line under every figure: source, unit, window, updatedOur World in Data, mevboost.pics, relayscanSection footer line
7Unknown flow stays visibleorderflow.art "Unknown", relayscan caveats"Not in the top 20 apps" node
8Methodology in tiers: strip, per-metric note, one full pagegrowthepie, Artificial Analysis, orderflow.artBadge, Method toggle, docs page
9Scatter with a Pareto line for price against speedArtificial AnalysisModel detail (the price board)
10Compare picker capped small, state in the URLL2BEAT compare, Rated (2nd)Pin up to 4 rows (phase 2)

What to avoid: the 13-section single scroll (Artificial Analysis, OpenRouter rankings), rankings with no entity comparison (OpenRouter), credits above the hero (orderflow.art), sidebar sprawl (DefiLlama, 2nd).

Rules from the literature

RuleSource
Overview first, zoom and filter, details on demandShneiderman 1996
At most two disclosure levelsNN/g, Progressive Disclosure
No tabs between things readers compare; one page with in-page navigationNN/g, Tabs Used Right; In-Page Links
57% of viewing time is above the foldNN/g, Scrolling and Attention
Same anatomy everywhere ("meaningless variety" is pitfall 6); a number needs "compared to what"Few, Common Pitfalls in Dashboard Design
Side-by-side compare holds 5 items at most; drop attributes most items lackNN/g, Comparison Tables
Frozen first column, right-aligned figures, unit in the header, sorted by valueNN/g Data Tables; UK Analysis Function
Bars in one column only; sparklines on a common scale when rows are comparedDatawrapper; Few
Never a blank cell or a false zero: [x] not published, [z] not applicable, [e] estimatedUK Analysis Function, symbols in tables
Sankey: order nodes to cut crossings, bucket weak links into Otherdata-to-viz; EU Data Visualisation Guide
Ranks overstate differences; show n or an intervalGoldstein and Spiegelhalter 1996
Mobile: sticky header, frozen first column, hide secondary columnsNN/g Mobile Tables

Not settled by any authority: Sankey node limits, how many key numbers above the fold, global against local controls. Those are our calls.

2. Decisions

  1. One page, a rail, seven numbered sections. Same rail and anatomy as the probe tab. No sub-tabs, no page per layer.
  2. Comparisons live inside each layer section as the side-by-side table. No separate comparison group. The top-level Compare tab keeps its meaning (asserted against measured).
  3. Identical section anatomy: header band (number, name, question, source badge, Method), at most three key numbers of which one is always coverage, one share figure, one side-by-side table, one source line. Everything else is a fold.
  4. Superseded 2026-09-19: one window control (1, 7, 30 days) drives every section whose source allows it, and the rest state their fixed window in the header. Original decision: No global controls. Sources cover different windows (OpenRouter a week, Vercel rolling, Requesty April) and only OpenRouter providers have dollars. A global window or unit would misstate most sections. Toggles stay inside the section that supports them.
  5. No total across routers. Units differ (tokens, shares, spend). The Routers table has a "publishes" column instead.
  6. Thin layers stay visible. Hardware keeps the anatomy with a coverage number and [x] cells.
  7. The per-model price board becomes the detail of a model row, not a top-level section. Click a model in the Sankey or the Models table and its provider board opens in place (scatter with Pareto line, provider rows).
  8. Public and private is a section and a filter. Its own section 6, plus an "attested" column in Models and Providers.
  9. The look does not change. Colours, type, Sankey and particle canvas stay.

3. Wireframes

Page

 The market | Our probe | Compare | Taxonomy and method
┌ rail ────────────┬───────────────────────────────────────────────────────┐
│ THE FLOW         │ 0 Overview     Where does inference flow?   [reported] │
│  0 Overview      │   101T tokens/wk · 88 providers · 1.4% attested        │
│ THE STACK        │   ┌ Sankey: app → model → provider → attested? ──────┐ │
│  1 Apps          │   │ OpenRouter, one day. Top 8 per stage + Other.    │ │
│  2 Routers       │   │ "Not in the top 20 apps" stays visible (61%).    │ │
│  3 Models        │   └──────────────────────────────────────────────────┘ │
│  4 Providers     │   The stack                leader        coverage      │
│  5 Hardware      │   1 Apps       20 named    Hermes 12%    39% of tokens │
│ CROSS-CUT        │   2 Routers    6           OpenRouter    2 of 6 tokens │
│  6 Public and    │   3 Models     20 + 59     GPT-5.6 Luna  full          │
│    private       │   4 Providers  88          …             full          │
│                  │   5 Hardware   [x]         [x]           1 of 88       │
│                  │   6 Private    4 attested  1.4% tok / 1.7% usd         │
│                  ├───────────────────────────────────────────────────────┤
│                  │ 1 Apps   Which apps send the flow?  [reported] [Method]│
│                  │ …                                                      │
└──────────────────┴───────────────────────────────────────────────────────┘

The stack strip is both the summary and the navigation: each row jumps to its section.

Layer section (Providers shown; row values are placeholders)

─────────────────────────────────────────────────────────────────────────────
4 Providers   Who serves it, at what price, speed and uptime?
                                         [reported + measured by others] [Method]
  88 providers      top 3 hold 28% tok / 41% usd      HHI 497 tok / 796 usd

  ┌ share by provider, 90 days, top 8 + everyone else ─── [tokens | dollars] ┐
  └──────────────────────────────────────────────────────────────────────────┘

  Side by side                 sort any column · attested only ☐ · show all 88
               ── volume ────  ── price ───  ── service ────────  ── trust ──
  provider     tokens/day  %   vs builder    cache  tok/s  TTFT  up%  tier  TEE
  DeepInfra    ████ 1.9T  10   −38%          61%    94     1.2s  99.9 no-store ·
  Chutes       ██   0.9T   5   −52%          [x]    71     1.9s  98.1 confid.  ●
  …
  [x] not published · [e] estimated · TTFT and up% measured by TrustedRouter, n per row
  ▸ Concentration over time (HHI)
  openrouter.ai providers · tokens · 90 days · updated 2026-09-19 · TrustedRouter leaderboard
─────────────────────────────────────────────────────────────────────────────

Section contents

#QuestionKey numbersFigureSide-by-side columnsFolds
0 OverviewWhere does inference flow?tokens/wk, providers, attested shareSankeythe stack stripnone
1 AppsWhich apps send the flow?named apps, top app share, tokens with an app namedapp categories, one barapp, category, tokens/wk, requests, tokens per requesttask mix in other populations (ChatGPT, Claude.ai); Claude share by agent (Requesty)
2 RoutersWhich routers carry it, and how do their mixes differ?routers, how many publish tokens, open-weights rangeone 100% bar per router by lab, same lab order and coloursrouter, publishes (tokens, shares, spend), volume, window, open-weights %, top lab, top model, updatedKilo 63 weeks by lab; Vercel labs over time; OpenCode by country
3 ModelsWhich models, from which labs?models, open-weights share, top lablab sharemodel, lab, open weights, tokens/wk, % on OpenRouter, % on Vercel, % on OpenCode, providers, price min to max, attested providers. Row opens the provider boardpulls outside routers (Ollama, Hugging Face); AI Horde
4 ProvidersWho serves it, at what price, speed and uptime?providers, top-3 share, HHIshare by provider over 90 daysas drawn aboveconcentration over time
5 HardwareWhat silicon serves it?providers that publish silicon (coverage)Darkbloom chipsquantization by endpoint count, TEE-capable endpoints; silicon column [x]none
6 Public and privateHow much is attested, and by whom?attested share tok / usd, Chutes TEE share, confidential routes (TrustedRouter)attested share over time, tokens and dollarsprovider, attestation, verified by registry, verified by TrustedRouter, volume and its unit, TTFT, availabilityChutes by its own meter; Darkbloom network; registry coverage; privacy tiers of 1,763 routes

4. Phases

  1. Restructure. Rail, anatomy, stack strip, move existing figures, build the six tables from data already collected. Sankey trimmed to top 8 per stage plus Other. Mobile: tables freeze the first column and hide secondary groups; Sankey swaps for one stacked bar per layer.
  2. Detail and compare. Row opens in place (trend, upstream and downstream). Pin up to 4 rows. State in the URL hash.
  3. Hardware. A short list of providers that state their own silicon, each linked to its statement and labelled as unverified. Everyone else stays [x]; nothing is assumed to be a GPU.

5. Sources

Sites: orderflow.art, l2beat.com, relayscan.io, mevboost.pics, growthepie.com, ultrasound.money, artificialanalysis.ai, openrouter.ai/rankings, vercel.com/ai-gateway/leaderboards, epoch.ai, arena.ai/leaderboard, gs.statcounter.com, inferencex.semianalysis.com, ourworldindata.org. Second-hand only: defillama.com, rated.network, radar.cloudflare.com, tokenterminal.com.

Literature: Shneiderman, "The Eyes Have It" (1996). Few, "Common Pitfalls in Dashboard Design" and "Best Practices for Scaling Sparklines". NN/g: Progressive Disclosure; Tabs, Used Right; In-Page Links; Scrolling and Attention; Comparison Tables; Data Tables; Mobile Tables. UK Government Analysis Function: tables guidance; symbols in tables. ONS service manual: chart text; annotations. Datawrapper: tables guide. data-to-viz: Sankey. EU Data Visualisation Guide: Sankey and alluvial. Goldstein and Spiegelhalter, "League Tables and Their Limitations" (1996).

6. Motion ("juice"), added 2026-09-20

"Juice" comes from the Experimental Gameplay Project (Gamasutra, 2005): "constant and bountiful user feedback". Jonasson and Purho ("Juice it or lose it", 2012) and Nijman ("The art of screenshake", 2013) made it a craft; Kelly ("Don't juice it or lose it", 2014) and Kao (2020: medium juice beats both none and extreme) are the cautions. For a measurement site the rule is narrower: motion may say where something went or that an input was received, and may never show a value that was not measured (Heer and Robertson 2007: "maintain valid data graphics during transitions").

What movesHowWhy
Buttons, chips, tiles, rail linkscolour in 100 ms; press scales to 0.97input received
Flow diagram hover and isolateribbon and node opacity in 120 mswhich flow is being read
Table sort, filter, pin, show allrows slide to their new place in 220 ms (FLIP); over 50 rows or more than a screen of travel, a 120 ms dissolve; a newly pinned row gets one mint tint that fades in 600 msthe same rows, in a new order
Row detail, Method, folds, the estimate cardfade and 4 px in 150 to 160 ms; the card grows from its markit belongs to what was clicked
Window changesections dissolve in 140 ms; numbers and charts swap at once, nothing morphsnew data on the same axes
Tab changeone marker slides under the tabs in 180 ms; content swaps at oncewhere you are
Particles in the flow diagramthe only ambient motion; "pause motion" stops them and is rememberedmotion that starts by itself must be stoppable (WCAG 2.2.2)

One easing everywhere, cubic-bezier(.2,0,0,1). Opacity and transform only. Everything is off under prefers-reduced-motion.

Never: count-up numbers, charts that draw themselves in, bounce or overshoot on any mark, scroll-triggered reveals, parallax, shake, sound, pulsing badges, anything over 300 ms.

Sources: Gabler et al., "How to Prototype a Game in Under 7 Days" (2005). Swink, Game Feel (2008). Kao, "The effects of juiciness in an action RPG" (2020). Heer and Robertson, "Animated Transitions in Statistical Data Graphics" (2007). Bostock, "Object Constancy". Robertson et al., "Effectiveness of Animation in Trend Visualization" (2008). NN/g, "Animation Duration". Kowalski, "7 Practical Animation Tips". Lewis, "FLIP Your Animations". WCAG 2.2.2 and 2.3.3.

7. The data tab, added 2026-09-21

Dan's ask: a tab that shows all the data we have, the rough schemas and tables, the size, the last sync date and how far it goes back. Code: the #tab-data block in index.html and site/data-ui.js. Everything on it is read at load from api/v2/overview.json (the counts: every table and board with rows, bytes, columns, first and last period, last sync, tier, public flag) and, where served, api/v2/tables.json (the columns), api/v2/boards.json (what a board measures, its URL, metrics, citation) and api/v2/sources.json (operator, license, redistribution, citation, terms). Nothing but labels is written in the page.

Same anatomy as the market tab, no new visual language: rail, five numbered sections, header band with the question, source badge and Method, key numbers, one figure, one side-by-side table per section, a key line and a source line.

#QuestionKey numbersFigure or tableRow detail
0 OverviewWhat do we hold, and how far back?tables, boards (public and private), sources, rows served (plus rows on private boards), bytes on disk, oldest period, newest syncthe timeline strip: one row per market table and per leaderboard source, a bar from first period to last, a tick at last sync, public and private by tone, undated rows grouped at the bottom; every row is a button that opens its table or source belownone
1 TablesWhich tables exist, what does each hold, how big is it?nonetable, what it holds, group, rows, size, columns, first and last period, last sync, tier, served, files (parquet, csv, guide)every column with type, unit, tier, key and description; a copyable DuckDB one-liner over HTTP
2 BoardsWhich leaderboards do we read, what does each measure?nonesource, board, what it measures, ranks, period, rows, first and last period, last collected, tier, license, redistribution, served; filter "public only"metrics with unit and direction, the board's URL, license, citation, mapped-row share
3 SourcesWho publishes it, under which license?nonesource, operator, kind, tier, license, redistribution, boards (public of total), rows, first and last period, last sync, servedhomepage, terms, citation line, how and how often it is read, every board of the source (each opens its row)
4 How to use itHow do I read a table, what may I do with it?nonethe DuckDB and pandas one-liners, the board_entry manifest, the snapshot rule in three sentences, license and citation, the public and private rulenone

Rules kept: dates as YYYY-MM-DD, sizes in decimal MB with one decimal (KB under 0.05 MB, so no false zero), [private] on rows that are counted and not served, [undated] on tables without a period column, † on a table the dictionary lists and the overview did not count, no bare number as navigation (the strip rows carry names), no count-ups or draw-ins, the strip rows and copy buttons are buttons and so reachable by keyboard.