How we verify our data

Current confidence

Degraded

Data is available, but one or more trust signals are degraded. Review affected routes and freshness details.

Latest snapshot age: 22h ago

View methodology Open latest transparency snapshot Augea Research See affected routes

When data is incomplete, we say so. When a route cannot be ranked, we show why. Unknown is first-class, not hidden.

Estimates, not quotes.

ACTIVE EXCHANGES

COUNTRIES

ASSETS

ACTIVE ALERTS

Snapshot: #32777 · 2026-06-23T00:16:14.724Z Alerts and provenance

Latest snapshot

#32777 · 2026-06-23T00:16:14.724Z

22h ago

Freshness coverage

432

Fresh rows currently visible

INTERPRETATION · TRUST SURFACE

What this trust surface can show, and what it cannot prove yet

The trust surface reads from the same captured evidence that powers every Augea estimate. The columns below separate what the captured evidence supports right now from honest gaps — coverage varies by country, asset, rail, and exchange.

EVIDENCE AVAILABLE

What this evidence can show

FRESH ROWS: 432; Currently visible rows inside the freshness window.
STALE ROWS: 1; Captured rows past the freshness window — surfaced honestly, not hidden.
RANKABLE ROWS: 432; Rows clearing the rankability gate (≥ 5 distinct exchanges, fresh, complete).
LATEST SNAPSHOT: #32777 · 2026-06-23T00:16:14.724Z; 22h ago

EVIDENCE INCOMPLETE

What this evidence cannot prove yet

Live-now state — every value is captured at a specific timestamp; verify before acting.
Per-exchange withdrawal speed, hold periods, and minimum amounts — not yet tracked at scale.
Routes outside the captured country / asset / rail universe — coverage varies and unknown is first-class.
Future state — captured evidence describes what was true at capture time, not predictions.

SOURCEAugea Public Trust Dashboard

CAPTURED22h ago

METHODOLOGYRead methodology

FRESHNESS · CAPTURE CADENCE

Freshness states at a glance

Each point shows the captured state at the moment of the latest snapshot. Stale, unknown, and missing-snapshot states are visible, never hidden.

Fresh
Fresh rowsCurrently visible rows inside the freshness window.
432
Stale
Stale rowsCaptured rows past the freshness window — surfaced honestly, not hidden.
1
Fresh
Latest snapshotCapture timestamp for the most recent snapshot.
22h ago

COVERAGE · RANKABILITY BREAKDOWN

Coverage states at a glance

Each point shows how rows in the latest snapshot break down across the rankability gate. Unrankable and no-snapshot states are visible, never hidden.

Rankable
Rankable rowsRows clearing the rankability gate (≥ 5 distinct exchanges, fresh, complete).
432 / 433
Unrankable
Unrankable rowsRows in scope but missing one or more critical fields for ranking — surfaced honestly, not hidden.
0 / 433
No snapshot
No-snapshot rowsRows with no captured snapshot for the latest cadence — coverage gap remains visible.
1 / 433

How Augea verifies estimates

Augea trust status

Every estimate is tied to a snapshot timestamp and source context.
Methodology is public and linked from every trust-first surface.
Unknown and incomplete states are displayed explicitly, not hidden.
Editorial accountability stays with Augea; no silent model overrides.

What we don't do

No pay-for-ranking.
No guessing missing values.
No selling user data.
No personalized ranking.
No guaranteed prices.

When we get it wrong

Failure modes include stale snapshots, coverage regressions, and missing evidence fields.

We detect them through snapshot diffing, confidence degradation checks, and explicit unknown-state accounting.

When detected, we surface the degraded/unknown state and retain provenance instead of masking uncertainty.

Trust Transparency Index

Latest edition

No public Trust Transparency Index edition is published yet in this deployment.

When available, this slot will link to the latest edition and archive history.

Incidents & corrections

Public incident window: 32776 to 32777.

Confidence degradation events detected: 0.

Technical appendix (raw proof and controls)

How it works

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.

Snapshot pipeline

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

Unknown rows

What user sees: You see cost ranges with snapshot provenance.

System health

Live system health

Coverage, ranking eligibility, and freshness remain explicit even when data is unavailable.

Snapshot: #32777 · 2026-06-23T00:16:14.724Z

Coverage

Active exchanges59

Countries13

Assets18

Unavailable metrics (1)

Exchange-country pairsNOT_AVAILABLE

Ranking eligibility

Total rows433

Rankable rows432

Unrankable rows0

Unknown rows1

Rankable rate99.8%

Unavailable metrics (1)

Partial rowsNOT_AVAILABLE

Freshness

Fresh432

Stale1

Unrankable due to freshness0

Not available0

Data change tracking

Alerts and provenance

Compare snapshots to see what changed and when.

Snapshot: #32777 · 2026-06-23T00:16:14.724Z

Alerts

Confidence degradation events0

Window32776 -> 32777

Alert statusOK

Snapshot provenance

Snapshot: #32777 · 2026-06-23T00:16:14.724Z

Scenario audit

Pepe · Norway · Card

PEPE · NO · Card

Back to /buy Share trust view

Scenario audit not available

No scenario snapshot is available for this asset and country.

Back to /buy