Market context
Public benchmark · Evidence-grade results

Compare route cost with the evidence attached.

Every result keeps its timestamp, source freshness, methodology, confidence state, and caveats. It is decision support—not advice or execution.

Evidence path

A number is useful only when you can inspect how it was produced.

Start with the comparison; open the evidence envelope when you need to challenge it.

Evidence loopObserve quotes to Compare costs to Attach evidence to Publish record. Each record informs the next comparison1Observequotes2Comparecosts3Attachevidence4PublishrecordEvidence loopEach record informs the next comparison
  1. 01Observe quotes
  2. 02Compare costs
  3. 03Attach evidence
  4. 04Publish record
Data feed health
Snapshot files updated in the last 24h. This is storage upload age, not per-snapshot observation time.
—
of — current
Methodology versions
sandwich-detector v0.4.2
schema 2026.06.13
api routescore.public_api.v1
route score routescore.route_score.v1
hash 9f2ca14e8b07d361fb40c2
How to read results

A highlighted result means lowest observed cost under this methodology (for live quotes) or lowest modeled cost under this methodology (for modeled scenarios) — a point-in-time, methodology-scoped comparison, not advice and not a promised outcome. A comparison is only named when at least two independent quotes were observed.

Outside RoutescorePlan to Preflight to Execute elsewhere to Record. Execution happens elsewhereROUTESCORE · READ-ONLYEXECUTION BOUNDARY1Plan2Preflight3Executeelsewhere4RecordOutside RoutescoreExecution happens elsewhere
  1. 01Plan
  2. 02Preflight
  3. 03Execute elsewhereOutside the read-only boundary
  4. 04Record
Observed · Live venue quotes

Same intent, multiple venues

Loading the latest venue-quote observations…

Modeled · Preflight scenarios

Built from the same shared model functions as the public API — lowest modeled cost under this methodology

preflight_action.v0

Computing modeled scenarios in your browser…

Scenarios are computed in your browser from the same shared, pure model functions the product and the public API build on (launch-static-v1 launch static route catalog — a versioned modeled assumption set, not a live quote feed). The API check additionally resolves a single route, applies request validation, and attaches its own trust envelope — this page shows the full ranked comparison from those shared functions, not a byte-identical API response. Modeled, point-in-time decision support; figures are not measured executions and not promises of any result.
Published · Weekly editions

Frozen Route Quality Index editions — citable weekly artifacts

pay_to_rank: false
Edition
#4
ISO week
2026-W32
Headline RQI
not verified
Claim state
no_data
Observation source
live warehouse — no observations yet
Methodology
route_quality_index.v1
Published
2026-08-03
Artifact hash · index-listed
sha256:e392de7f7e8105c…
Edition
#3
ISO week
2026-W30
Headline RQI
not verified
Claim state
no_data
Observation source
live warehouse — cohort-level labels only (no venue-attributed observations yet)
Methodology
route_quality_index.v1
Published
2026-07-20
Artifact hash · index-listed
sha256:b097c3391b5cf77…
Edition
#2
ISO week
2026-W29
Headline RQI
not verified
Claim state
no_data
Observation source
live warehouse — cohort-level labels only (no venue-attributed observations yet)
Methodology
route_quality_index.v1
Published
2026-07-13
Artifact hash · index-listed
sha256:f526928beb94a03…
How to read and verify these editions
Editions rank only genuine warehouse-provenance venue-attributed labels and are frozen at publish. The hash column is read from the mutable editions index — it is a pointer, not proof; the frozen edition page carries the full citation block (edition number, ISO week, methodology version, full artifact hash, canonical URL) to verify against. When the live feed is cohort-level (as it is today), the headline reads “no venue data” — a first-class state, never a fabricated number. All editions: /rqi
Evidence records · Verification path

How a result becomes citable evidence

Read-only API evidence pipelineA keyed swap preflight is evaluated, persisted, linked, retrieved, independently verified, and labeled later. If persistence fails, linkage fields return null. Routescore never executes the swap or holds keys.ROUTESCORE · READ-ONLY BOUNDARYDECISION SUPPORT · NEVER EXECUTES · NEVER HOLDS KEYS1KEYED POST/check/swapsubmit preflight input2EVALUATEread-only resultscore routes; no execution3PERSISTpreflight_record.v0store immutable evidence4LINKrecord_id + hashreturn citable linkage5RETRIEVEGET /records/{id}fetch the evidence record6VERIFYSHA-256re-derive canonical digest7LATERoutcome labelsettlement reconciliationPERSISTENCE FAILEDrecord_id: nullhash: nullexplicit caveat;nothing fabricated

Every keyed, evaluated call to POST /api/public/v1/check/swap attempts to persist a routescore.preflight_record.v0 evidence record. On success, the response body (excluding the record-linkage fields returned alongside it) is nested in the record, and the response returns a record_id plus a record_output_hash — that record_id is the citable reference for the check. If persistence fails, the response says so via a record_persistence_failed caveat and those fields return null.

retrieve GET /api/public/v1/records/{record_id}
verify re-derive the sha256:-prefixed canonical-JSON digest per the exact recipe in the evidence-records guide — it must equal integrity.output_hash

Anyone holding a record can re-derive the hash independently — the normative third-party recipe (which fields are excluded, key ordering, serialization semantics) is in the evidence-records guide. The in-page results above are unkeyed computations and scanner observations, so no record was minted for them and no record_id is shown — record ids on this page are never fabricated.

Outcome-label path: every persisted check carries an outcome-label slot that starts pending. Realized-outcome labels accrue via independent settlement reconciliation — never at decision time. Aggregated calibration evidence is founder-gated and not yet public; until it is, the record itself (retrieve + re-derive the hash) is the verification path. API access: /developers.

Operating motto

Measure in public. Price the risk. Never touch the keys.

Observable route traces converge into a measured risk band while a key remains isolated beyond the read-only boundary.