Trust Dashboard
See how we track, verify and maintain the data behind every estimate.
When data is incomplete, we say so. When a route cannot be ranked, we show why. Unknown is a first-class state, not a failure.
Estimates, not quotes.
Snapshot: #1062 · 2026-03-26T00:05:07.287Z Alerts and provenance
From raw data to verified estimate
How a scenario moves from raw exchange data to a verified, rankable estimate — or an explicit unknown.
Estimates, not quotes.
1.A scenario tuple is resolved from asset, country, payment rail, and priority.
We identify exactly what you are comparing.
2.Snapshots collect exchange evidence for that scenario at a capture time.
We pull real cost data from each exchange.
3.Rows are validated for required fields and explicit evidence flags.
We check whether the data is complete enough to use.
4.Coverage pointers publish the latest valid snapshot for display surfaces.
We publish the latest verified data.
5.Pages render explicit state: rankable, partial, or no snapshot.
You see exactly what we know — and what we do not.
Example values only. Not quotes.
Example interaction
Step 0 / 4
Scenario input: BTC / US / card / 1000
Rankable scenario
All displayed rows carry required fields and evidence flags.
Truth state
RANKABLE
Known rows
3
Unknown rows
0
What user sees: You see cost ranges with snapshot provenance.
System health
Coverage, ranking eligibility, and freshness remain explicit even when data is unavailable.
Snapshot: #1062 · 2026-03-26T00:05:07.287Z
Coverage
Unavailable metrics (1)
Ranking eligibility
Unavailable metrics (1)
Freshness
Alerts and provenance
Compare two snapshots to see what changed between them.
Snapshot: #1062 · 2026-03-26T00:05:07.287Z
Alerts
Snapshot provenance
Snapshot: #1062 · 2026-03-26T00:05:07.287Z