Every number on Claveta is a real count of distinct verified businesses — rounded down, never inflated, and shown only once it clears a published reliability floor. Below the heart of Claveta is one promise: the score is never for sale.
Here is exactly how each verification tier is earned, beside its live count.
We don’t ask you to trust us — every verified fact on our public changelog (and on each order’s receipt) names the exact free, public check we ran and its result, so a skeptic can re-run the same check and get the same answer:
rdap.org/domain/<domain>); the registration date gives the age.notAfter date we show).dns.google/resolve?type=MX&name=<domain>) for an MX record.Every check is free, key-free, and run against the same public source we used. To protect the listed businesses we mask names and never publish a contact (email / phone / website / address) — the result itself is the proof.
Transparent 0-100 composite of the live verified-tier counts, normalized by businesses_indexed. For each tier, term = min(distinct_verified_in_tier / businesses_indexed, 1.0); score = round(100 * (0.50*T3 + 0.30*T2 + 0.20*T1)), weights T3>T2>T1, summing to 1.0. Read-only and DERIVED from verified counts only; with 0 businesses indexed the score is 0. NEVER sold or alterable for money (no pricing/billing/treasury module may import it) — the score is never for sale.
Every verified fact has a half-life: it only counts while it is fresh (within 30 days), and a daily re-verification re-runs the original check so a live source stays counted and a dead source ages to zero. Median fact age: 0 days. (Honest counts: share floored, age rounded down.)
Every lead from public Google Maps listings; freshness = scrape timestamp
EU VAT ids checked live against official VIES; only confirmed-valid counted
Domain age via public RDAP; older domains flagged established
Public Google Maps presence with a real review count
Live HTTPS cert valid now — independent of domain age
Delivered emails checked via ZeroBounce; only status=valid counted; we never claim every row is verified
Domain publishes an MX record (checked live via public DNS-over-HTTPS); proves the domain can RECEIVE mail — NOT that any address is deliverable
Phone parses to a valid dialable E.164/national FORMAT (offline check); attests the FORMAT only — NOT that the line is answered or connected
Transparent 0-100 composite of the live verified-tier counts, normalized by businesses_indexed. For each tier, term = min(distinct_verified_in_tier / businesses_indexed, 1.0); score = round(100 * (0.50*T3 + 0.30*T2 + 0.20*T1)), weights T3>T2>T1, summing to 1.0. Read-only and DERIVED from verified counts only; with 0 businesses indexed the score is 0. NEVER sold or alterable for money (no pricing/billing/treasury module may import it) — the score is never for sale.
Refund policy is replacement-first then refund within the published 14-day window; every refund issued is logged as a real event (COUNT db.guarantee_stats: 0 refunds, 4 orders fulfilled).
Median of (delivery timestamp − order timestamp) over fulfilled orders, measured from real logged events (db.sla_stats); we report the share completed in under 60 minutes, floored — never rounded up (median ≈ 0 min over 0 measured deliveries).
The strongest trust signal is naming our own boundaries. Each live check below attests exactly one thing — and we state, in the same breath, what it does not prove. We would rather under-claim than mislead.
Our heart principle is independence: the Veridio score has no write-path from money. This is not a promise — it is enforced in code by a grep-assert that fails the build if any pricing, billing, or treasury module so much as imports the score. We re-run that exact assert on every request and show you the live result:
PASS: no money module references the score.
We just re-ran the check, live, against this exact deploy: pricing.py, billing.py and treasury.py import NEITHER the score symbol nor its getter/setter. The Veridio score has no write-path from money.