Draft v0.1 — open for public comment. Endpoint examples are illustrative. The verification program and index are in preview.
Open specification · Draft v0.1

Conformance

Four levels, earned with evidence. Recomputed as evidence changes.

What each level requires

L1 · Described

A valid record is published. Business claims remain self-asserted.

L2 · Callable

Required actions pass live probes and response validation. Probe history is published.

L3 · Verified

Required credentials pass independent checks and synthetic transactions succeed.

L4 · Monitored

Continuous probing and current, independently checked trailing-90-day outcomes.

L1 is a described record with self-asserted business claims. L2–L4 require verifier-computed evidence. Publishing a number in JSON does not earn that level. A verifier also establishes domain control before endorsing a record.

Earned, then re-earned

Liveness evidence expires after 24 hours. License and insurance evidence expires on the authority's cadence or after 90 days, whichever comes first. Expired required evidence is excluded; the highest still-supported level is recomputed.

A failed required credential check or seven consecutive days of failed probes causes suspension. The endpoint remains visible with the reason and date, but leaves default ranking until re-verified.

Where are you today?

This checklist is a local planning aid. Checking boxes does not verify an endpoint or transmit an application.

Preflight and the conformance suite

The browser preflight checks structure, formats, required capability actions, and price ordering. The full suite — live probes, consented synthetic transactions, credential checks, and evidence freshness — is still planned. Preflight is not that suite.

Run preflight · Follow the draft.