> For the complete documentation index, see [llms.txt](https://docs.blerify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blerify.com/introduction/what-is-blerify.md). # What is Blerify Blerify is a digital identity infrastructure platform that lets governments and enterprises issue tamper-proof credentials, lets people carry those credentials on their phone, and lets any organization verify them in seconds — without calling back to the issuer. *** ## Who it's for **Issuers** are organizations that want to put their credentials on a user's phone: a government agency issuing national IDs, a university issuing diplomas, a financial institution issuing KYC status, a professional body issuing licenses. Blerify handles the cryptography, the trust registry, and the delivery — the issuer provides the data. **Holders** are the people who receive credentials into the Blerify Wallet. They control what they share and with whom. No credential leaves their phone without their biometric approval. **Verifiers** are organizations that need to confirm something about a person — age, identity, employment status, professional license — without storing the underlying document. They call a small API and get back a verified result. *** ## What you can issue and verify Blerify supports two credential formats: **W3C Verifiable Credentials** — the JSON-LD / JWT format defined by the W3C. Use this for any credential whose schema you define: employee badges, academic diplomas, insurance cards, professional certifications. **ISO 18013 mDocs (mDL)** — the ISO standard for mobile driving licenses and government-issued identity documents. Use this when you need interoperability with government systems or ISO-compliant readers. Both formats are signed with the issuer's cryptographic key, anchored in a decentralized trust registry, and verifiable offline. *** ## Real use cases in Latin America **National digital identity.** A government agency issues citizens a digital version of their national ID card. Citizens receive it in the Blerify Wallet; banks, telecoms, and retailers verify it at onboarding without photocopying anything. **Professional licenses.** A professional body issues digital licenses to doctors, lawyers, and engineers. Hospitals and law firms verify the license via API before granting system access — no phone calls, no registry lookups. **Academic credentials.** A university issues diplomas and transcripts as W3C credentials. Employers verify them instantly. The university doesn't need to run a verification hotline. **Employee digital badges.** A company issues a digital work credential to contractors and full-time employees. Physical access systems, HR portals, and benefits platforms verify the credential in the same flow as a standard API call. **Financial KYC.** A regulated financial institution issues a KYC-passed credential to customers who've already gone through identity verification. Partner organizations can accept that credential without running their own KYC — the cryptographic proof travels with the holder. *** ## How Blerify relates to open standards Blerify implements open W3C and ISO standards — not a proprietary protocol. Credentials issued on Blerify are interoperable with any wallet or verifier that supports: * OpenID for Verifiable Credential Issuance (OID4VCI) * OpenID for Verifiable Presentations (OpenID4VP) * ISO 18013-5 for mDocs This means holders are not locked into the Blerify Wallet and verifiers are not locked into the Blerify API. Where interoperability matters, credentials work beyond the Blerify ecosystem. *** ## The four products Blerify ships as four independent products, each with its own portal, API, and access control: | Product | What it does | | ------------------ | ------------------------------------------------------------ | | **Issuance** | Issue W3C credentials and ISO 18013 mDocs to holders | | **ID Wallet** | The mobile app where holders receive and present credentials | | **Verification** | Verify credentials presented by holders | | **Trust Registry** | The decentralized record of who can issue what | Each product is documented in its own section. You don't need all four — most integrations use two or three. Post-Quantum Certificates is a feature within Issuance, not a standalone product — see [Post Quantum Certificates](/introduction-to-issuance/post-quantum-certificates.md). *** ## Next steps * Understand the full issuance-to-verification flow in [How It Works](/introduction/how-it-works.md) * Start issuing credentials in [Issuance — Get Started](/introduction-to-issuance/build/get-started.md) * Start verifying credentials in [Verification — Get Started](/introduction-to-verification/build/get-started.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.blerify.com/introduction/what-is-blerify.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.