Live verification · no authentication

Verify any LQS cert in real time.

Procurement teams, auditors, regulators, and buyers can cryptographically verify any LabelSets cert without an account. Paste a cert hash below to check the Ed25519 signature, revocation status, and the full procurement payload.

Public endpoint: /api/verify-lqs-cert/:cert_hash Try the live demo → Trust Center
?
—
—
—
LQS composite
Tier
—
95% CI
—
Scorer version
—
Scored at
—
Issuer
—
Key source
—
cert_hash —
public_key_id —
Oracle consensus
Benchmark contamination
Downstream projection
Task-conditional routing
View raw signed payload (for offline re-verification) 
—
Examples
Valid · gold tier
Example production cert
Live-signed, verifies cleanly. Shows the full procurement payload.
27a8060ab73c…915b25ce
Not found
Unknown cert hash
A hash that doesn't exist in the registry. See what "not found" looks like.
0000000000…00000000
Offline verify
Verify without hitting us
Use the public key + Python SDK for air-gapped verification.
pip install labelsets
How verification works

Verifiable without trusting us.

Every LQS cert is an Ed25519-signed canonical JSON payload. Anyone with the public key can verify a cert offline. If we went offline tomorrow, every cert we've ever issued stays verifiable using the public key you already have.

1
Fetch the cert
Query the public verification endpoint with the cert hash.
curl /api/verify-lqs-cert/$HASH
2
Fetch the public key
Ed25519 public key for offline signature verification.
curl /api/lqs-public-key
3
Verify offline
No trust in us required — re-check the signature yourself.
pip install labelsets
labelsets.lqs_offline_verify(cert, pk)
Try it · zero server contact

Verify a cert in your browser.

Paste a full cert envelope JSON below. We use the Web Crypto API (crypto.subtle.verify) to check the Ed25519 signature against the public key. No LabelSets server contacted for the verification step itself — only to fetch our published public key once. View source to confirm.

Web Crypto API · checking…