Obtain an API key from Credential Engine and your organization's CTID (Credential Transparency Identifier) via the registry at https://credentialengine.org/
Use the sandbox endpoint https://sandbox.credentialengine.org/assistant/credential/publish for testing; production endpoint is https://apps.credentialengine.org/assistant/credential/publish
Construct a CTDL JSON document with required fields: @context (https://credreg.net/ctdl/schema/context/json), @type (ceterms:Certificate, ceterms:Badge, or other ceterms: subtype), ceterms:name, ceterms:description, ceterms:subjectWebpage
POST the CTDL document to the publish endpoint with Authorization header: ApiToken YOUR_API_KEY; the body is a JSON wrapper with @graph array containing the credential object
On success the API returns an envelope with CTID, registryURL, and payload; save the CTID for future updates and DELETE operations
Use GET https://credreg.net/graph/{CTID} to verify the published record is publicly accessible in the Registry
Known gotchas
The Authorization header must use the literal text 'ApiToken ' (not 'Bearer ') before the key value; using a standard Bearer scheme returns 401 Unauthorized
CTDL requires at least one ceterms:ownedBy pointing to an organization CTID that is already registered in the Registry; publishing a credential without a valid owning organization fails with a validation error
Sandbox and production use separate API keys and CTIDs; a credential published in sandbox does not appear in production search results and vice versa
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