A verifiable credential is a credential whose authenticity and current status a third party can confirm directly with the issuer, without having to trust the holder's copy. Anyone relying on it can see it was really issued, to whom, for what, and whether it is current, lapsed or revoked. The proof lives with the issuer, not in the document.
Why does verifiability matter for AI agent oversight?
Approval rights over agents increasingly depend on credentials. A team lead may release held payments only if certified; a contractor may review drafts only if current. Each of those rules needs a credential that can be checked at the moment it is relied on. A certificate that only exists as a file can be edited, outdated or copied, and nobody looking at it can tell.
Verifiability also saves effort. An employer onboarding twenty contractors does not need to call twenty training providers. Each credential carries a number or QR code that leads straight to the issuer's record.
How does it work in practice?
A verifiable credential typically has:
- a unique identifier, such as a certificate number, and often a QR code;
- a verification page hosted by or for the issuer;
- the holder's name, the credential, issue date and expiry;
- a live status that changes when the credential lapses or is revoked;
- protection against tampering, so a changed copy does not match the record.
The person relying on it scans or enters the identifier and reads the status on the issuer's page. Status is the point. A credential verified as genuine a year ago tells you nothing about today; credential expiry explains why, and expiry is what makes a credential honest argues the principle.
What is an example?
A private clinic introduces an agent that drafts appointment and referral letters, with a practice manager approving those that involve clinical information. The clinic's insurer asks for proof that approvers are trained. Instead of sending files, the clinic sends certificate numbers. The insurer checks each on the issuer's page: all current, expiry dates visible. When one manager's certificate lapses months later, a re-check shows it at once. Clinics face this question often; see how private clinics prove staff are trained.
How is it different from a verifiable digital certificate?
The terms overlap. A verifiable digital certificate is a specific document: a certificate issued digitally with a link back to the issuer's record. A verifiable credential is the broader idea, covering certificates, licences, badges and other attestations that share the property of being checkable with their issuer. Every verifiable digital certificate is a verifiable credential; not every verifiable credential looks like a certificate.
What matters in each case is the credential issuer: who keeps the record and whether they keep it current.
Which terms are related?
- Checking at source: the act of verifying with the issuer.
- Public register: a list of verifiable credentials searchable by name.
- Revocation: withdrawing a credential before it expires.
For the wider topic, read AI literacy and certification for people who work with agents.
Where the Academy fits
Pryme Intelligence Academy certificates are issued through VerifyDoc.ai and can be checked at source by anyone, by number or QR code. A lapsed or revoked certificate shows as such on the same page, and a public register lists certified people by name, credential and expiry.
Questions people ask
Is a PDF with a QR code a verifiable credential?
Only if the QR code leads to the issuer's live record and the status there can change. A QR code that opens a copy of the same PDF proves nothing.
Does verification reveal personal data?
It reveals what the issuer publishes on the verification page, usually name, credential, dates and status. Issuers should limit it to what a relying party needs.