Docs · For recruiters

Verify 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.

Verify 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 (completion)

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 (held-out)

Coming

A separate, harder tier is coming: earned by passing a held-out problem the course never taught, server-graded with no AI pair-programmer, certifying a single named skill. Until it ships, no profile shows a Verified badge — so today a completion credential resolves to a positive, signed “Authentic · lab-graded” result, not “held-out Verified.”

Our verifier reserves the emerald “Verified” headline for held-out credentials. A completion credential resolves to a positive, signed Authentic · lab-graded — a real, cryptographically authentic record of AI-assisted lab coverage, no more and no less.

How verification works

You don’t have to use our widget — the format is open and the check is reproducible. One honest caveat: it uses our open-source verifier today, not a generic W3C VC library (standard-library interop is on the roadmap).

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?