For certification & training programs
Not files. Not platforms. Verifiable credentials for certification and training programs, over open standards.
Credentials are issued as Open Badges 3.0. They stay meaningful in any tool that supports the spec.
We onboard a small design-partner cohort with direct access to the team. Not a self-serve floodgate before the product is ready.
Each credential opens a page anyone can use to see it is real. No account. No paywall. Just the link you share.
What is OpenCredia?
Credentials today live as files or inside closed platforms. OpenCredia makes them signed, portable, and independently verifiable, over one API. You build credentials from templates, tie them to the right people, and each one gets a link anyone can use to see it is real, without guessing whether a PDF was forged.
Senda Academy
Issuer
Elena Vargas
Certification
Applied Team Leadership Certificate
Senda Academy
Credentials wallet
Claimed
Credentials verifier
Verified
No silos. No proprietary formats. Credentials that move with the recipient and work in the tools (and verifiers) that support the same open standard.
How it works
Principles
Learners and alumni keep portable credentials in their own wallet. They move with the person, not a single vendor.
Each credential is signed and comes with a check people can run, in a browser or through your product, without "trust me" screenshots.
Native Open Badges v3 and W3C Verifiable Credentials. Use the same records in any wallet or tool that supports the spec.
A REST API with idempotent writes and scoped keys when you are ready to wire credentials into onboarding, an LMS, HR, or a product you ship.
Capabilities
Public verification and APIs are how teams plug OpenCredia in. The rest is what keeps your program able to issue, your recipients able to keep what they earned, and your security story straightforward.
A verification page for every credential, plus a JSON API your stack can call. We validate signatures, revocation, and shape, and public reads do not need an API key.
Call OpenCredia from your backend with predictable REST, idempotent writes when you retry, and errors you can act on, not guesswork.
Template-driven issue at scale: batches, rollouts, and a clear record of what was sent.
Tie each credential to the right person, email, DID, or an id you bring, with deduplication to avoid double issue.
A hosted wallet for recipients to claim, share, and download their credentials in seconds.
Each organization has its own signing key, stored encrypted, used to sign credentials and status lists. Self-serve key rotation is not built yet.
Built for developers
No dashboards required. Just calls.
Issue, revoke, and verify with predictable calls. Idempotent writes, scoped API keys, and a verification endpoint you can point anything at, including unauthenticated reads for public checks.
POST /v1/credentials/issue
Authorization: Bearer opencredia_live_<your-api-key>
{
"templateId": "ai-leadership",
"recipient": {
"email": "[email protected]"
},
"metadata": {
"issuedAt": "2026-04-22",
"cohort": "spring-26"
}
}Standards
The credential is not locked to one vendor. Recipients can take it with them. Anyone can verify it without an account.
The format recipients can take into other wallets and tools. Issued to the Open Badges 3.0 spec.
Learn more (1EdTech OBv3 spec)A signed proof, not a screenshot. Compatible tools can check it without logging into OpenCredia.
Learn more (W3C VC Data Model)Issuers can publish a public did:web so verifiers can see who signed it. Recipient DIDs are accepted as IDs.
Learn more (W3C DID Core)Who we're building with
We onboard one cohort at a time. If you run a program, embed issuance, or hold credentials that need to travel, we want that first conversation to be with you.
Organizations
Issue a cohort without standing up signing, keys, or revocation. One API ships the batch with a public page anyone can check in a browser. The program still looks legitimate when an employer asks.
Issue your first verifiable credential in under ten minutes once you are onboarded. Open standards, a clean API, and a wallet your users actually own.