The OilFlow data flywheel, in numbers.

Every metric here is pulled live from the same tables the production routes write to. No aggregation, no editorial. We publish because corpus depth is unfakeable — a competitor would have to operate for years to match these numbers, and at small N the trajectory matters more than the headline.

Generated at Thu, 23 Jul 2026 01:47:05 GMT · Refreshes every 30 minutes · Source: live Supabase tables (predeal_checks, broker_scam_blocklist, verified_profiles, defense_packs, cluster_submissions)

Pre-Deal decision corpus (SKU #5)

The labeled training-data flywheel. Every /api/v1/predeal/check call writes one row.

136

Total checks ever

99

Checks last 30 days

35

Outcomes attributed

25.7% attribution

75.7

Avg clearance probability

Across all checks (sample n≤5000)

48

Aggregable rows

Feed cross-customer corpus (Moat 2)

88

Private rows

Bank Enterprise opt-out (Moat 2)

Outcome distribution (sample n≤5000)

OutcomeCountShare
Unmarked (not yet back-filled)10174.3%
Abandoned3525.7%

Cluster intelligence (SKU #3)

First-party investigated fraudulent counterparty clusters. Every row was originated by an OilFlow investigator, not aggregated from public lists.

426

Active cluster entities

2

Confirmed severity

Verifiable fraud

8

Likely severity

Shell + fictional entities

416

Suspected severity

Routing-layer patterns

63

Countries touched

Customer cluster contributions (SKU #3 corpus flywheel)

The customer-contribution surface added 2026-06-07. Every submission feeds the OilFlow IP.

0

Submissions total

0

Pending triage

0

Accepted last 90d

→ new blocklist rows

0

Duplicates last 90d

Same entity, two reporters

0

Rejected last 90d

Insufficient signal

Verified counterparty network (Two-sided moat)

Counterparty-side opt-in for the +15 clearance lift in Pre-Deal Copilot. Document-backed approvals carry more weight.

0

Approved profiles

0

Pending approval

0

Document-backed approved

— of approved

Avg docs per approved

Across document-backed profiles

Defense-pack regulatory ledger (SKU #6 scaffold)

Every MLRO-signed pack carries a SHA-256 hash binding evidence + decision + signoff. Independently verifiable via /api/v1/defense/[id]/verify.

1

Total packs

1

Signed packs

MLRO-attested

0

Hash-chain bound

0% of signed

0

Draft packs

0

Rescinded

Original hash preserved

Methodology

Every number on this page is a live aggregate from the production database. We do not curate, redact, or re-state. Counts in some tables (Pre-Deal outcomes, cluster severity) are computed against a 5000-row sample to keep the page response fast at scale; in current corpus sizes the sample equals the whole table. If you want an independent count of any of these, the table names are public and the API endpoints write them.

We publish because corpus depth is the moat. A startup competing with OilFlow tomorrow would have to operate for years to match these numbers. We'd rather show the trajectory honestly than inflate a headline.