Schema
OK
The evidence entry exists and has a valid structure.
#000261
Compliance evidence · TSP-verified certificates
Verification status
LEXI-2026-AAB91C4CE775B169
Issued to
Trust
The verification shows who issued the certificate, what was completed, which regulatory basis applied, and whether the TSP signature and evidence chain are intact.
Audit package
This verification can be shared as machine-readable JSON, a public certificate profile and TSP chain status. No email address, user id or internal payloads are exposed.
Privacy
The verification gives an auditor enough information to check status, issuer, certification basis, regulation version and TSP evidence without exposing unnecessary personal data.
Email is not shown on public verification or in the JSON endpoint.
Internal user ids and LexicoUserId are not shared.
Internal company and tenant ids are kept out of public verification.
Address, phone and payment data are not shared.
Raw answers and internal assessments are not published.
Signed internal payloads and audit notes are not exposed publicly.
Schema
OK
The evidence entry exists and has a valid structure.
#000261
Content integrity
OK
The recalculated hash matches the signed hash.
SHA-256
Chain
Failed
The hash chain up to this entry is intact.
37/38
Signature
OK
The Ed25519 signature is valid for the issuer key.
Ed25519+RFC3161-SHA256
All four checks must pass for the evidence to count as verified.
You do not need to trust Lexico to verify this evidence. Download the public key (PEM) and the issuer manifest, and check the signature offline with any Ed25519 tool: recalculate the SHA-256 over the signed fields and verify the signature against the key. The procedure is documented in the TSP specification.
Assessment evidence
The certificate binds a cryptographic hash of the exam answers into the signed evidence. A third party can confirm exactly what was answered, without any raw answers or personal data being present in the evidence.
This certificate has no bound answer hash (older certificate or not exam-based). The TSP signature itself still verifies.
Cryptographic proof that the assessment was carried out as recorded. It proves what the person answered and that it is unchanged since signing — not that the person «understands» in an absolute sense, and it is not in itself legal compliance.
This page shows publicly verifiable status without exposing private keys or internal user data beyond the certificate proof itself.
Your Academy account
Create or connect an account to see your own certifications, certificates and learning status.
The Trust Standard Protocol (TSP) is an open protocol that makes AI decision evidence durable, tamper-evident and verifiable offline — by anyone, without having to trust the vendor. Every event is signed with Ed25519, hashed with SHA-256 over canonical JSON (JCS, RFC 8785) and chained to the previous entry.
TSP verifies the integrity of the evidence — not whether the content is true, lawful or compliant. TSP does not make you compliant, does not prove that a model is correct or safe, and grants no official status. Payment never grants official status. The legal assessment remains with your DPO and legal advisers.
TSP is currently operated by LexiCo AS (Norway, EU/EEA) as operator and licensee — not as owner of the standard and not as a certification authority. The open layer (specification, test suites, verifiers, TrustBadge) is Apache-2.0 licensed.