Verification Standards
How credentials are verified.
A credential that cannot be independently verified is, in practice, a graphic. Kindra credentials are verifiable directly with the institution at any time — by the holder, by a hiring manager, by a registrar, or by a curious peer. This page documents exactly what that verification establishes.
Last reviewed · May 2026
The verification page
Every credential has a permanent public verification URL of the form /verify/{CODE} on the Kindra domain. The page is public — no account is required to view it. The page loads its data from the institution’s authoritative record, not from any information embedded in the credential graphic itself.
What the verification page establishes
- That a credential with this code was issued by Kindra AI University.
- The name of the course of study completed.
- The date the credential was issued.
- The recipient’s name as it was recorded at the time of issuance.
- That the credential has not been revoked.
What it deliberately does not establish
- It does not establish that the recipient is currently employed in any role.
- It does not establish that the recipient is an expert in the field.
- It does not establish proficiency at a defined level (Kindra credentials do not certify mastery — see Credential Methodology).
- It does not expose any personal data beyond the recipient’s name as enrolled.
Unknown codes
A request for a verification code that does not exist returns a clean “no record found” institutional response. The page does not attempt to disambiguate, suggest alternatives, or accept partial codes. Either a credential exists with that exact code, or it does not.
Why we do it this way
The point of an institutional verification standard is that it is boring, deterministic, and external. The hiring manager, the peer, the friend — they should not need to take the holder’s word for it, and they should not need to ask Kindra anything by email. The page is the source of truth.
Questions about this document? registrar@kindraai.dev