Review the CEASN schema documentation at https://credreg.net/ctdl/handbook for the ceasn:CompetencyFramework and ceasn:Competency class definitions
Construct a CTDL/CEASN JSON-LD document with ceasn:CompetencyFramework as the root type, including ceasn:name, ceasn:description, ceasn:publisher (org CTID), ceasn:dateCreated, and ceasn:hasPart referencing an array of ceasn:Competency objects
Each ceasn:Competency must include ceasn:competencyText, ceasn:competencyLabel, and optionally ceasn:educationLevelType mapped to a CTDL education level URI
POST the document to https://apps.credentialengine.org/assistant/competencyframework/publish with Authorization: ApiToken YOUR_API_KEY; the sandbox endpoint uses sandbox.credentialengine.org
Retrieve the published framework via GET https://credentialfinderapi.credentialengine.org/api/competencyframework/{CTID} to confirm public availability
Link the competency framework to a credential by adding ceterms:requires or ceterms:recommends in the credential CTDL document, referencing the framework CTID
Known gotchas
CEASN uses a different type hierarchy than CTDL credentials; publishing a ceasn:CompetencyFramework to the credential/publish endpoint (instead of competencyframework/publish) results in a schema validation error
Competency URIs within the framework must be unique and persistent; using temporary or auto-generated URIs breaks inbound links from credentials referencing those competencies
The Registry enforces that the publisher organization exists and is verified; unverified organizations cannot publish to the production Registry
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