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

Trust badges & attestations

A badge people can inspect. A signed claim machines can verify. Both start with evidence.

The badge

The planned badge shows current L2 Callable, L3 Verified, or L4 Monitored standing and links to the endpoint's report. A copied image does not prove identity or verification. The report and evidence are authoritative.

SAMPLE ONLY — L3 illustration, not valid verification

Sample data — demonstration only. No valid program badges are issued in this preview. Live badges must update on downgrade or suspension, include their endpoint identity, and link to the current report.

Demonstration embed:

<!-- Sample only. This is not valid verification. -->
<a href="https://verifiedserviceschema.org/reports/com.stainmydeck">
  <img src="https://verifiedserviceschema.org/badges/com.stainmydeck.svg"
       alt="SAMPLE ONLY — not valid verification" width="240" height="64">
</a>

Signed attestations

The planned program issues JWS compact serialization signed using ES256. An attestation is evidence of a claim at a time, not a guarantee of future performance. This is an unsigned illustrative payload, not a token:

{
  "as_of": "2026-09-16T07:00:00Z",
  "capabilities": [
    "home.exterior.deck_staining"
  ],
  "conformance_level": 3,
  "endpoint_id": "com.stainmydeck",
  "expires_at": "2026-09-17T06:00:00Z",
  "issuer": "https://verifiedserviceschema.org"
}

The program's key URL is /.well-known/jwks.json. It currently contains an empty key set because no production keys or attestations have been issued.

Verification steps for agents

  1. Establish trust in the issuer independently of the submitted record.
  2. Obtain that issuer's JWKS through a trusted channel. Offline verification uses a previously fetched trusted key set.
  3. Require alg: ES256, select an authorized key by kid, and reject signature failure.
  4. Match the expected endpoint identity, domain binding, capabilities, and required level.
  5. Reject invalid or expired as_of / expires_at windows. An attestation cannot outlive its supporting required evidence.
  6. Check a current report for suspension or revocation when present standing matters. A historical signature alone is insufficient.

Do not accept an arbitrary issuer or key URL simply because the token supplies it.

What verification is not

It is not a completion guarantee, insurance, bonding, a warranty, or a professional license. It is not transferable to another endpoint. It states which evidence supported a claim at the stated time.