Schemas, programmable
The schema side of the credential fabric.
VCT Registry hosts SD-JWT VC type metadata: what a credential is, what claims it carries, how to display it. While Trust Registry answers 'who can issue?', VCT Registry answers 'what are they issuing?'.
What VCT Registry does
A public-HTTP metadata resolver for SD-JWT VC type identifiers. Given a vct URL, returns the credential's schema, display info, and versioning metadata — cached aggressively so verifiers don't hit it on hot paths.
Differentiators
Why teams pick it
Standard + cached
5-minute Cache-Control means verifiers don't hit this service on hot paths. Schemas still cycle through quickly.
Versioning built in
Deprecation + superseded_by let you evolve credential types without breaking outstanding credentials.
Complementary to Trust Registry
Same admin surface can manage both: who can issue + what they issue.
Thin, public, stable
The product does one thing. No surprises.
Applications
What you can build
- Industry-wide credential schemas — A sector body publishes VCTs like HealthcarePractitionerLicense; all member issuers use the same schema.
- Government attestation schemas — A member state hosts VCTs for its qualified attestations.
- Wallet-facing display metadata — A wallet resolves vct → render 'Driving Licence' with icon + description.
- Verifier schema discovery — A verifier doesn't need schemas in its config; it resolves them at runtime.
Shipped today
- products.vctRegistry.shipped.items.s1
- In-memory stub registry with seeded demo VCTs
- 5-minute Cache-Control + application/vc+sd-jwt-vc-metadata+json content-type
- Public resolver surface usable from any verifier or wallet
On the roadmap
- Postgres persistence + admin API — CRUD for VCTs; operator-managed
- Versioning model — URL-embedded semver with deprecation
- Trust Registry UI cross-linking — navigable issuer ↔ VCT relationship
Ready to publish your credential schemas?
Request access to host VCT metadata with caching, versioning, and admin controls.