NEW TO THIS? START HERE
What’s a Learning Record Store?
An LRS is the system of record for learning activity — a database that stores every “who did what” event as a structured xAPI statement (“Maria completed Fire Safety, scored 92%”). Conformance means checking required standard behavior so data written by one tool can be read correctly by another. When an LRS is only partly conformant, that’s where integrations quietly break — a signature that won’t validate, a query that returns the wrong set. The 1,435-check result is evidence for the build that was tested. A current hosted-release claim requires a fresh run in an isolated, production-equivalent environment.
What you control
Behaviors covered by the conformance test run.
Statements API
Store, void, and query statements with full filter and paging semantics — verbs, objects, results, and 2.0 context agents/groups.
Document resources
State, Activity Profile, and Agent Profile documents with correct merge, list, and delete behaviour.
Signed statements (JWS)
Validates JWS signature attachments and X.509 certificates so tamper-evident records verify correctly.
Attachments
The local test run exercised multipart/mixed transport, SHA-2 integrity hashing, and attachment retrieval.
Document concurrency
ETag generation with If-Match / If-None-Match preconditions, so concurrent writers never clobber each other.
2.0-native context
contextAgents and contextGroups, ISO 8601 precision, and version negotiation built in from the start.
XAPI 2.0 CONFORMANCE RESULTS
1,435 passed • 0 failed
Our tested LRS implementation passed the ADL xAPI 2.0 suite. The suite tests mandatory requirements of the standard. Engineering test result; not an independent certification.
Local conformance-suite run dated 2026-06-06 · suite 5bc232d · hosted re-verification pending
Test configuration and scope
The June 6 run used a local Next.js development server with an in-memory backend. It is a historical implementation result, not a qualification of the current hosted Convex-backed service. Current release qualification needs an isolated, production-equivalent Convex-backed rerun. The retained result does not identify the tested application commit; raw per-check logs are not included in this summary. ADL advises against running this suite on a production LRS because its test data persists.
- ADL LRS Conformance Suite · v2_0
- 1435/1435
- ADL LRS Conformance Suite · v2_0
- 100%
- Suite
- ADL v2_0 @ 5bc232d
- Suite
- Run date
- 2026-06-06
- Run date
- Spec
- IEEE 9274.1.1
- Spec
- Failing
- 0
- Failing
FOR THE TECHNICAL BUYER
Point your content at the endpoint.
A standard xAPI 2.0 endpoint with HTTP Basic (or Bearer API key) auth, version negotiation, and the full Statement, State, Activity Profile, Agent Profile, Activities, Agents, and About resources. Map the Basic password to a Connect API key and you’re writing statements.
- Endpoint:
/api/lrs/xapi· Basic & Bearer API key · scoped authority - X-Experience-API-Version negotiation on every request
- Statements mirror in from SCORM dispatch & the hosted player
- Run qualification only against an isolated, non-production endpoint; the suite persists test data.
# Method summary, not an executable command
Suite revision: 5bc232d
Target: isolated non-production LRS
Setup and credentials: follow pinned ADL README
The suite persists test data.
# Historical June 6, 2026 local in-memory result
1435 passed / 0 failedStatus, limits and plans
- Status
- Available
- Plans
- The integrated LRS is included on every current plan. See plans
- Limits
- xAPI 1.0.3 statement ingestion and queries in production
- cmi5 package launch is not currently available
- Conformance evidence: Platform proof
- Docs
- SCORM CMI data guide
Questions about xAPI 2.0 Learning Record Store
What is an LRS?
Which xAPI version does Connect accept in production?
What did the xAPI 2.0 conformance run test, and what did it not?
5bc232d) in a local in-memory test configuration. It is self-reported engineering evidence, not an independent certification and not a rerun against the hosted service. See Platform proof.PAIRS WITH
Works with
- Available
SCORM Dispatch
Send content to supported SCORM-compatible LMSs; recorded completions are mirrored into this LRS.
- Available
Developer API & webhooks
Webhook every statement to your warehouse or CRM; GPT Actions included.
- Beta
Skill Graph
Roll up the statements in your LRS into a living model of who can do what.