Check any GenBodha credential yourself — in seconds

Every GenBodha credential is cryptographically signed and states its own method. The signature verifies in your browser against our public key — no login, no GenBodha account, no trusting us. Paste a candidate’s credential link below and check it.

Check a credential

Paste the genbodha.ai/credentials/… link from a candidate. Verification runs in your browser against our public key and signed revocation list — we never see your check.

What a GenBodha credential proves

Authentic · lab-graded

The candidate built working code that passed graded labs across a measured share of a discipline. Labs are AI-assisted, with Claude Code, hints, and a per-step answer reveal — so you can't get stuck. Auto-graded on running code. It’s graded on running code — not a quiz, not a watched video — and the record is a recruiter-auditable skill graph. It is not a proctored exam or an unaided test.

Verified

Not yet available

GenBodha does not yet issue its Verified credential in any discipline. Every GenBodha credential issued today is a Completion credential and resolves to a positive, signed “Authentic · lab-graded” result. The Credentials page lists what is available and the date that last changed.

How verification works

You don’t have to use our widget — the credential JSON, our public signing keys, and the signed revocation status are all public endpoints, and the check runs in your browser. One honest caveat: it uses our verifier today, not a generic W3C VC library (standard-library interop is on the roadmap).

GenBodha credentials use the W3C Verifiable Credentials format (the signing format, not the Verified checkpoint): an open standard for signed digital credentials.

They fetch our public key once from /.well-known/did.json.
They verify the Ed25519 signature in the browser against that key.
They check revocation against a public, signed status list, or hit /api/credentials/{id}/verify for a one-shot active/expired/revoked answer.
They get a yes/no in seconds — the only calls to us are the public key and the status list, both public, signed endpoints.

If we tampered with the credential, the math fails. If the candidate tampered with it, the math fails. That’s the point.

Was this page useful?