Sample data — demonstration only. Lookup results, reports, badges, and statistics are illustrative until the live program launches.
Evidence before trust · Program preview

How verification works

Every check carries a timestamp, a source, and an expiry.

Publish, probe, check, monitor

StepEvidence and outcome
Publish a Service RecordA structurally valid, stable record describes the operator, capabilities, coverage, actions, and pricing. Business claims remain self-asserted at L1. Domain control is established before this program endorses a record.
Pass live probesAll required action contracts validate and respond in scheduled, consented probes. Public history supports L2. A single successful call is not a track record.
Prove required credentialsIssuing-authority or other documented independent checks cover the vertical's required credentials. Synthetic transactions complete safely end-to-end. These support L3.
Stay monitoredContinuous probing and independently validated trailing-90-day completion and dispute data support L4. Evidence is refreshed before expiry.

These are planned program operations. The preview does not call real booking endpoints, charge payment methods, or perform background credential checks.

Five statuses

StatusMeaning
unverifiedNo valid published record or no independently supported standing. Level 0.
self_assertedValid L1 record; business claims come from the operator.
probedRequired actions pass probes and validation. L2.
verifiedRequired credentials and synthetic transactions pass. L3–L4.
suspendedRequired credential failure or seven consecutive days of failed probes. Public reason and date; excluded from default ranking. Level 0.

What we check

CheckWhat it establishesTypical source
liveness_probeAn action answers at the check time.Program prober
schema_validationA record or response matches its declared schema.Validation suite
synthetic_transactionA consented quote, availability, booking, status, and cancel cycle works.Test harness and endpoint sandbox
license_checkRequired professional credential is current at check time.Issuing authority
insurance_checkRequired coverage is documented.Carrier confirmation or reviewed COI, with the method disclosed
identity_checkOperator identity meets the stated verification policy.Identity provider
domain_ownershipThe operator controls the endpoint domain.DNS challenge or well-known file

Extensions define exact check sets. Proposed legal, home, and beauty policies are not Official in this preview. A reviewed document and direct carrier confirmation must be described as different evidence methods.

Freshness rules

Suspension is public

A failed required credential check or seven consecutive days of failed probes triggers suspension. The endpoint stays visible with its reason and date. It leaves default search until evidence supports reinstatement. Payment cannot override a failure. Appeals process.