store learner preference data in an xAPI Agent Profile document independent of any activity
domain: adlnet.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the agent (learner) and a profileId under which to store the data
PUT the profile document (arbitrary JSON, e.g. accessibility or UI preferences) to the Agent Profile resource with the agent and profileId
GET the profile back using the same agent and profileId to confirm storage
Use GET without a profileId to list all profile ids stored for that agent, filtered optionally by since timestamp
Apply ETag/If-Match on updates the same way as the State API to avoid overwriting concurrent writes
Known gotchas
Agent Profile documents are scoped only to the agent, never to an activity — using it to store activity-specific data is a spec misuse that breaks portability
Like the State API, concurrent updates without If-Match can silently overwrite another client's profile document
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?