Trust
How verification works
The plain-language version. Every credential is free to verify in seconds.
What a credential contains
A credential records what was built, the scores per challenge, the criteria and assessment version used, and the conditions recorded at issuance. Account email is omitted. Sharing a link does not prove that the viewer is the learner.
How it's protected
Signed
The record is signed when issued. Verification recovers the signing address and checks it against the authorized issuer and issuance window.
Fingerprinted
Its contents produce a unique fingerprint (a SHA-256 hash). Change one character and the fingerprint changes.
Anchored
The pilot stores fingerprints in EKO's local registry. Verification checks the fingerprint, signature, issuer policy and revocation list. Chain publication is paused; a legacy transaction reference is not treated as confirmed chain proof.
How grading is disclosed
Every credential prints its grading mode - structural checks, held-out AI-run tests, or code execution - and its rubric is published on the track page. Legacy assessment quality has not been independently validated. A valid signature authenticates a record; it does not establish competence.
API
Verification is available as JSON for recruiters and platforms: GET /api/v1/verify/{credential-id}. Free, no key required. Employers can generate keys from their report page for tracking.
Privacy
Interview answers and reports are private. Public credential records show their signed payload, without account email. Details are in the privacy policy.