Trusted Records · Integration & Developer
OpenAPI and Swagger Reference
The proposed contract is rendered from one local specification; no network Try-It or real credentials.
Proposed contract • read only
Swagger UI 5.33.1 • OpenAPI 3.1.1 • example OAuth .invalid • network Try-It disabled. Use the separate Explorer for simulation.
Continue the workflow
Two journeys, one records lifecycle
Connect paper and born-digital records through persistent identifiers, policies and evidence.
Read detailsIntegration quickstart
Exercise ingest → job tracking → registration → verification with synthetic data.
Read detailsIntegrity, provenance and evidence
Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment