Skip to content

Ecosystem — other ACDC schema registries

ACDC (Authentic Chained Data Container) credential schemas are published by several organizations across the KERI ecosystem. Because every schema is identified by its SAID (a content hash), the same schema is identical wherever it is served — a static site, a KERI OOBI endpoint (/oobi/{said}), or a source repository. This page indexes the registries we know of; the machine-readable version is registries.json.

Registry Operator Resolution Links Notes
Bakobo (this site) Bakobo static repo · registry General-purpose ACDC schemas, GCD chief among them; browsable pages + machine manifest + per-SAID OOBIs.
Provenant public-schema Provenant oobi repo · registry The repo bakobo forked from; general + telco/vLEI types. Served via a KERI schema-registry (S3+CloudFront), application/schema+json.
vLEI (GLEIF) GLEIF / WebOfTrust static repo · — The vLEI credential family (QVI, LE, OOR/ECR + authorizations, iXBRL attestation). No longer OOBI-only: since 2026-08-05 GLEIF publishes a .well-known discovery surface — an RFC 6415 host-meta.json, a generated catalog, and each schema as browsable JSON at a stable per-SAID URL. weboftrust.github.io serves an identical surface from a byte-identical build script, so the two are one implementation published from two origins. The vlei-server OOBI endpoints remain the production resolution path.
WebOfTrust schema WebOfTrust source-only repo · — KERI/ACDC reference schemas (bindkey, designator-aliases, vLEI); carries its own registry.json and /oobi files. No confirmed public host.
Veridian Cardano Foundation unknown repo · — ACDC wallet + platform; Cardano-anchored credentials. Public schema-serving endpoint not confirmed.

resolution: static = browsable schema JSON at stable URLs · oobi = served via KERI /oobi/{said} · source-only = repository, no confirmed public host · unknown = host not confirmed.

Specifications

Publish your own

Adopt the discovery-manifest schema — serve a /.well-known/acdc-schemas.json conforming to it, and your registry is machine-discoverable by the same convention. Then open a PR adding an entry to federation.json.