llms.txt integration
Verify an llms.txt declaration
Paste a declaration (declarationId and canonical bytes, plus the signature if you have it). No Trustvice account required. A failed check is never shown as a pass. A matching content address without a verified signature is not signed authorship. A retired declaration can still verify — that does not make it current.
What this proves
- When the signature verifies and the registry was readable, the canonical bytes were signed by the published Emissary key named on the result, and they hash to the stated declarationId.
- When only the content address matches, the bytes have not been altered relative to that id — authorship is still unverified.
- Anyone can repeat this check with no Trustvice account.
What this does not prove
- Signed authorship when signatureVerified is false. A matching content address is not a green pass.
- That a retired declaration is still the live position. retired: true is cryptographically valid and superseded.
- Currency when registryChecked is false. That is unknown, never “not retired”.
- Anything about the AI Nutrition Label (Placard), Cachet, or Paradigm — those are separate public verbs.