For agent builders & AI engineers
Fetch it, verify it, build on it.
You want machine-readable controls, explicit schemas, evidence fields, stable identifiers, signatures, and runnable examples — not a PDF. Apeiris is an open, signed corpus you fetch, verify against a published trust anchor, and build on. You don’t have to invent the ontology, curate the controls, or maintain the framework mappings.
Start building
Everything is the data — the API is just the corpus, signed and pinned.
Run the reference implementation
In fifteen minutes: fetch one obligation, verify the signed manifest, resolve the addressing controls, and render the evidence each requires — one zero-dependency file.
A whole action on the wire
Schema-valid action-event → evidence-packet → decision — what a proven action actually looks like, coverage vs evidence.
The fetch → verify → use pattern
Quickstart, how to verify integrity before you trust an artifact, and how to cite a control by its stable apeiris:// URI.
API & endpoints
Every JSON data endpoint categorized with copy-paste curl examples, plus the unified MCP server and the portable verifier.
MCP for agents
One read-only MCP server over the whole signed corpus — ATLAS, graph, corpus, knowledge, reasoning, and research tool groups.
Verify integrity in-browser
Recompute every artifact’s SHA-256 against the signed manifest and check the Ed25519 signature — don’t trust, recompute.
Pin it, and it won’t move under you
Pin to contract_version (SemVer — the shape contract) and version (CalVer — the data release). The contract-diff gate fails any breaking change — a removed field, a type change, a weakened fail-closed default — unless the major version is bumped. Identifiers are stable, every artifact is hashed and the manifest is signed, and fail-closed defaults are published in the conformance contract. Build against it without fear of a silent break.
Available today vs. in development
The open corpus is usable now. The runtime platform that watches your environment is being built — we hold that line explicitly.
Available today
- The runnable reference implementation and schema-valid worked examples
- A read-only MCP server, a consumer SDK, and a portable corpus verifier
- Signed manifest + published trust anchor; contract + CalVer/SemVer pinning
- Stable
apeiris://identifiers for every control, source, and obligation
In development
- An evidence ingestion API and per-tenant evidence store
- A canonical enterprise-asset object model and fact→evidence normalizers
- An integration / connector SDK and the continuous ingest→map→gap loop
Run it in fifteen minutes
The reference implementation does the whole pattern in one file.
Not your role?