Review the OBI Endpoints documentation at https://www.credly.com/docs/obi_specified_endpoints which describes the Open Badges Infrastructure endpoints Credly exposes
Access badge assertion JSON via GET https://api.credly.com/v1/obi/v2/assertions/{issued_badge_id}; this returns an OBI 2.0-compliant assertion object for legacy verifiers
Access the badge class (template definition) via GET https://api.credly.com/v1/obi/v2/badge_classes/{badge_template_id}; response includes name, description, image, and criteria fields
Access the issuer profile via GET https://api.credly.com/v1/obi/v2/issuers/{organization_id}; response includes the issuing organization's name, url, and email
For OB 3.0 verification, Credly returns a signed AchievementCredential JSON-LD document with a DataIntegrityProof; retrieve via the Credly badge sharing URL with format=json query parameter
Build a verification workflow: fetch the assertion, resolve the issuer DID from the issuer field, verify the cryptographic proof, and check the credentialStatus (if present) against the status list URL
Known gotchas
Credly's OBI 2.0 assertion endpoints use the legacy assertion format; third-party systems expecting OB 3.0 JSON-LD must use the dedicated OB 3.0 endpoints, not the OBI 2.0 paths
Credly badge images referenced in badge class objects may be served from CDN URLs that require authentication for private badge templates; public badges return publicly accessible image URLs
Assertion IDs are UUIDs tied to individual issuances; programmatically iterating all assertions for an organization requires the Issued Badges list endpoint, not the OBI endpoints
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