What is Glemo?
One API to verify credentials from any issuer.
Glemo is a credential verification network. You're hiring, admitting or onboarding someone who claims a credential — a degree, a certification, a license. Instead of emails and 3–5 day manual checks, you make one API call and get a cryptographic verdict in milliseconds, for credentials issued by any issuer on open standards (W3C Verifiable Credentials 2.0, Open Badges 3.0).
Quickstart
Self-serve test key → first verdict in under 5 minutes.
API essentials
Authentication, test vs live keys, errors and rate limits.
Concepts
Credentials, DIDs, verification and revocation — the model.
Interactive reference
Every endpoint, generated from the OpenAPI spec, with try-it.
How it works
- Someone presents a credential — an id from Glemo's registry, or a portable signed credential (VC-JWT) issued by anyone.
- You call
POST /verifywith your API key. - Glemo runs the checks — signature, issuer identity (DID), schema, revocation status, validity window — and returns a verdict with the evidence.
Verdicts
Every verification resolves to exactly one of six deterministic verdicts — never a maybe:
| Verdict | Meaning | Typical action |
|---|---|---|
valid | Every check passed | Accept |
revoked | The issuer revoked it | Reject, show reason |
expired | Past its validity window | Ask for a renewal |
tampered | Signature or schema broken — content was altered | Reject, flag |
not_found | No credential with that id | Ask for the source |
not_verifiable | Issuer identity couldn't be resolved | Retry / manual review |
Ways to integrate
- API —
POST /verify, one call, any stack. Start at the quickstart. - SDK —
@glemo/sdkfor Node, browsers and edge, with typed errors. - Widget —
<glemo-verify>: paste a snippet, get a live verdict badge. No code beyond HTML. - Webhooks — signed notifications for every verification, for your async pipelines. See webhooks.