Export a complete competency framework as a single CFPackage from a CASE 1.1 REST provider.
domain: imsglobal.org · 5 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Locate the target framework's CFDocument identifier via GET /ims/case/v1p1/CFDocuments or a known package ID.
Call GET /ims/case/v1p1/CFPackages/{id} to retrieve the full package export in one request, rather than paging through CFItems and CFAssociations individually.
Parse the package into its CFDocument (framework metadata), CFItems (hierarchical competency nodes), and CFAssociations (relationships) components.
Check each CFAssociation's targetType before assuming the linked object exists within the same CASE package, since v1.1 supports associations pointing outside CASE entirely.
Cache or store the exported package rather than re-fetching the whole framework for small incremental needs.
Known gotchas
CASE is fundamentally a read/consumption-oriented provider API — don't assume a standardized write/publish-per-item endpoint exists; publishing is typically implementation-specific package upload.
Associations that reference non-CASE objects (via targetType) will not resolve to another CASE entity — check before treating every association as internal.
Large collection GETs still require pagination handling for CFItems/CFAssociations if you fall back to item-level queries instead of the full package export.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?