Verification endpoints
Confirm whether a reviewed artifact still matches the preserved history and return PASS, FAIL, or no-source states with verification details.
Endpoint Families
The API surface maps to real integration jobs.
Use these endpoint families to verify artifacts, manage evidence packages, and preserve relationships across source and derived records.
Evidence package endpoints
Create, read, update status, and retrieve standards-aligned evidence packages tied to preserved artifacts and review state.
Relationship endpoints
Represent learner, issuer, contributor, skill, rubric, source-artifact, and derived-output relationships without losing the artifact chain.
Verified Evidence Package
The evidence package is the object other systems should point to.
It is the bridge between raw verified artifacts and institutional systems that need portable, reviewable evidence.
Identity and issuer
Learner identity, issuer or school identity, and organizational references that establish who the evidence belongs to and who is asserting it.
Learning or program context
Course, pathway, program, class, skill, competency, or rubric references that explain what the artifact is being used to support.
Artifact and provenance
Verified media capture, C2PA manifest reference, hash state, source linkage, and trusted timestamp for artifact integrity.
Review and use state
Review status, evidence summary, verification URL, revocation state, and derived-output relationships that make later inspection possible.
Example Payload
See the structure of the evidence package.
The payload below shows how provenance, identities, competencies, review state, and public verification can travel together in one object.
Illustrative JSON
A standards-aware evidence package can combine provenance, identities, competencies, review state, and public verification in one object.
{
"package_id": "ao-evidence-2026-00142",
"learner_id": "learner-8842",
"issuer_id": "district-cte-12",
"program": "Advanced Manufacturing Pathway",
"competency": "precision_measurement_level_2",
"artifact": {
"artifact_id": "ao-artifact-58f2",
"media_type": "video/mp4",
"c2pa_manifest_id": "c2pa:manifest:8842",
"sha256": "6e4d...a1c9",
"sealed_at": "2026-05-22T14:05:11Z"
},
"review": {
"status": "approved",
"rubric_id": "rubric-mfg-precision-02",
"evidence_summary": "Learner demonstrated calibrated measurement workflow."
},
"verification": {
"public_url": "https://archiveorigin.com/public/verify/ao-evidence-2026-00142",
"current_result": "PASS",
"revocation_status": "active"
},
"targets": {
"open_badges": true,
"clr": true,
"lti_launchable": true
}
}
Standards Expansion
Map the preserved evidence object into existing systems.
Standards alignment lets schools, workforce partners, and credentialing systems reuse the same verified evidence object across their existing workflows.
1EdTech
The primary bridge into education interoperability because it governs credential, learner-record, and LMS-adjacent workflows.
Open Badges 3.0
Allows a credential to point back to verified evidence instead of existing as a badge with weak artifact support.
CLR 2.0
Lets verified evidence support learner records, pathway documentation, portfolio artifacts, and workforce-facing skill history.
LTI 1.3 and later OneRoster
LTI enables LMS launch and assignment workflows first. OneRoster can later connect class, roster, and enrollment context into the package graph.
Trust and Procurement
Institutional readiness matters at implementation time.
These standards and controls support security review, procurement review, accessibility review, and implementation confidence.
Trust stack
- C2PA for artifact provenance
- RFC 3161 timestamping for stronger evidentiary timing signals
- Public verification URLs for downstream review
- Future W3C Verifiable Credential alignment for portable trust objects
Institutional readiness
- FERPA-aware data handling expectations
- NIST and ISO 27001 alignment work for security maturity
- SOC 2 readiness for vendor review and institutional adoption
- WCAG expectations for accessible interfaces and review workflows
Next Step
Review the implementation path.
Archive Origin connects C2PA provenance, standards-aware evidence packages, verification endpoints, and institutional integrations into one technical workflow.