Obtain the Open Badges 3.0 specification from 1EdTech and confirm the AchievementCredential JSON-LD context and required claims (type, issuer, credentialSubject, achievement)
Generate or retrieve the issuer's signing key pair; construct the AchievementCredential JSON-LD document and sign it using a supported proof method (e.g., Ed25519Signature2020 or DataIntegrityProof) to produce the VC
Publish the issuer's DID document or JSON-LD key material at a resolvable URL so verifiers can retrieve the public key for proof verification
Deliver the signed VC to the earner via the OB 3.0 API endpoint or as a direct download; the earner stores it in a compliant wallet
Verify the credential by resolving the issuer key, checking the cryptographic proof, confirming the credentialStatus (BitstringStatusListEntry) is not set to revoked, and validating required claims against the AchievementCredential schema
Known gotchas
The issuer's public key URL must remain permanently resolvable; a key rotation without a migration plan breaks verification of all previously issued credentials that reference the old key
Open Badges 3.0 uses the W3C VCDM v2 context alongside the OB 3.0 context; omitting or mis-ordering the @context array causes JSON-LD processors and verifiers to reject the document
Platforms certified for OB 2.0 are not automatically certified for OB 3.0; check the 1EdTech certified products list before assuming a receiving platform can ingest VC-based badges
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp