Open
Open data model
Issuers and credentials are stored as plain JSON resources aligned with Open Badges and VC conventions.
Open Trust Infrastructure
Issue, host, and verify credentials as open resources with explicit trust checks. Built for schools, workforce teams, and learning platforms that need defensible proof.
Designed for high signal: open formats, durable identifiers, and transparent verification.
Open
Issuers and credentials are stored as plain JSON resources aligned with Open Badges and VC conventions.
Provable
Sign badge payloads with Ed25519 keys and verify them against issuer keys and hosted metadata.
Defensible
Domain validation and well-known issuer checks reduce impersonation and make trust boundaries explicit.
Not a new badge category, but a tighter operational stack with stronger default safety and automation.
Security
Public verify endpoints block private/internal targets before server-side fetches.
Trust policy
Well-known issuer verification, verified issuer registry, and safe test-domain handling.
Ops
Deploy-anywhere architecture with API, CLI, MCP integration, and llms.txt discovery surface.
From issuer setup to a verifiable assertion URL in a single pipeline.
GET /api/validate-issuer-domain
POST /api/issuer
POST /api/badge-class
POST /api/credential-subject
For issuers
Use API, CLI, or MCP tools to issue at scale with consistent validation and hosted JSON artifacts.
For verifiers
Provide a URL, JSON payload, or issuer profile to inspect structure, issuer validity, and signature status.
Free, interoperable credential trust rails. Same Firmament mission, tuned for operators and integrators.