Certificates and Badges

A certificate is a public page that shows a test's verdict and the evidence behind it, signed by llm-id.sh so that anyone can check it hasn't been altered. Badges link to it from your own site.

Issuing a Certificate

Open a test's report. Under Certificate, select Issue Certificate. You can issue one when:

• the test completed;
• its verdict is Genuine, or Abliterated with the identity check confirming the model;
• it finished less than 7 days ago.

An Abliterated certificate vouches that the endpoint serves the claimed model with its refusals removed in the weights: not a different model, and not the original behind a jailbreak prompt. It lists the refusal probes the endpoint answered and the prompt tokens it adds. An Abliterated verdict whose answers drifted so far that no model fits rests on the refusal probes alone, and isn't certified.

Issuing publishes the test's report: the endpoint address, the model name, the verdict, the evidence and the model's answers. Your API key is never part of a report. Each test has at most one certificate; issuing again shows the same one.

What It Shows

• No. LID- and the first 8 hex digits of the report's SHA-256 hash. The page lives at llm-id.sh/c/ and those digits.
• Issued and Valid Until. A certificate is valid for 7 days from the end of the test, because a model behind an endpoint can change at any time. Run a new test and issue a new certificate to keep one current.
• The verdict and the model, followed by the evidence: endpoint, model name, the model it was verified as, who served the requests, the identity fit, the routing check, the competence and refusal checks if they ran, the test's size and time window, and the reference data used.
• The seal: the report's SHA-256 hash drawn as a 16 × 16 grid, one cell per bit.
• The signature and the confidence of the verdict.

Checking a Certificate

Anyone can confirm a certificate without an account:

1. Download the audit report from the certificate page. Its SHA-256 hash must equal the seal.
2. Check the signed statement shown on the page. It names that hash, the endpoint, the model and the verdict, and its Ed25519 signature must verify with the llm-id.sh public key printed beside it.
3. Read the status. Expiry and revocation aren't part of the signature; the page and the badges show them as soon as they happen.

Badges

Under Embed a Badge in the report, pick a style, a ground and a format, then Copy the code into your site or README.

Each style comes for a dark or a light ground. A badge always reflects the certificate's current status: its verdict, Genuine or Abliterated, while valid, then Expired or Revoked. Badges refresh within five minutes of a change.

Revoking

Revoke in the report withdraws a certificate at once, for example after a change to the endpoint. The page and every badge then say Revoked. A revoked certificate can't be reissued from the same test; run a new test instead.