Checking a certificate at source means confirming it against the issuer's own live record, by number or QR code, instead of trusting the copy someone hands you. The copy shows what was true on the day it was printed. The source shows what is true now: whether the certificate is current, lapsed or revoked.
Why does it matter for people who oversee agents?
Approval rights over an AI agent are only as sound as the person holding them. If a reviewer may release held payments because they hold a current certificate, "current" has to be tested, not assumed. A file in a shared folder cannot show that a certificate expired last month or was withdrawn after an assessment finding. That is the argument behind why a PDF certificate proves nothing.
The same discipline already runs inside a governed platform for the agent itself. Its certificate is one of the five bounds checked at the moment of action, and a lapsed certificate stops the action. The people approving its work should be held to the same test.
How does a check at source work?
The checker enters the certificate number or scans the QR code and lands on the issuer's verification page. It shows the holder's name, the credential, the issue date, the expiry date and the status. Confirm three things each time:
- The name matches the person you are relying on, not just the document.
- The credential is the one the role needs, at the level it needs.
- The status reads current, and the expiry falls after the period of work in question.
Then note who checked, when, and what the page said.
What does it look like in a real team?
Take a claims team bringing in a contractor to cover a reviewer's leave. The contractor sends a certificate for reviewing agent decisions, valid for 12 months. The team lead scans the QR code. The page shows the certificate was genuine, but it lapsed two weeks ago because renewal was never completed.
The team lead puts the contractor in a shadow role until the source page shows the renewal. The copy was real, but only the source could say it was out of date.
How is it different from inspecting a certificate?
Inspecting a certificate means examining the document: logo, signature, layout, perhaps a watermark. It answers "does this look real?" Checking at source answers "is this true today?" A good forgery passes inspection, and so does a genuine certificate that has since lapsed. Neither passes a check at source.
Expiry makes the difference sharper. A person's certificate for overseeing agents typically runs 12 or 24 months; an agent's certificate lapses after 90 days. When it is the agent's certificate that has lapsed, the reviewer's position changes in other ways, covered in what a lapsed AI agent certificate means for a reviewer. Either way, as a certificate should say what someone can do today puts it, a credential is a claim about the present.
Which related terms should you know?
- Verification page: the issuer's page showing a certificate's live status.
- Lapsed: past expiry without renewal. Revoked: withdrawn by the issuer before expiry.
- Supervisor literacy: the wider skill set described in what AI literacy means for people who supervise AI agents.
The full topic sits in AI literacy and certification for people who work with agents.
Where the Academy fits
Pryme Intelligence Academy issues its certificates through VerifyDoc.ai, so anyone can check one at source 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. A business can tie approval rights to a certificate that is current when checked this way.
Questions people ask
Who should do the check?
Whoever grants approval rights, usually the team lead or operations manager, with HR keeping the note. Check at onboarding, before any change in approval rights, and on a fixed cycle after that.
Is a screenshot of the source page enough?
It proves the check happened on that day. It proves nothing about any later day, so re-check at source rather than relying on the screenshot.