Launch a cmi5 Assignable Unit from an LMS, handle the fetch URL token exchange, and post a Passed or Failed statement to the designated LRS endpoint
domain: aicc.github.io · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Parse the AU launch URL query parameters: endpoint, fetch, registration, activityId, actor
HTTP POST to the fetch URL with no body to exchange it for the LRS auth token; store the token, do not reuse the fetch URL
Send an Initialized xAPI statement to the endpoint using the actor, activityId, and registration from the launch params
Execute the learning content; on completion POST a Passed or Failed statement with a result.score.scaled value
Send a Terminated statement as the final statement of the session before closing
Verify all statements include the cmi5 context template category activity and the correct registration UUID
Known gotchas
The fetch URL is single-use; calling it twice will return an error and the AU will have no auth token
cmi5 requires statements to be sent in strict order: Initialized first, Terminated last; out-of-order delivery causes conformance failures
The moveOn criterion (Passed, Completed, CompletedOrPassed, etc.) is set by the LMS in LMS.LaunchData, not by the AU; the AU must send the matching statement type
Give your agent this knowledge — and 15,800+ more routes
One MCP install gives any agent live access to the full route map across 5,800+ 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?