> 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/welcome-to-blerify-docs.md).

# Welcome to Blerify Docs

Blerify is a digital identity platform for issuing and verifying credentials. You use it to issue verifiable credentials to end users — government IDs, professional licenses, access passes — and to verify those credentials at any point of interaction, on the web or on mobile.

This documentation is for developers building on top of Blerify: issuers, verifiers, and wallet integrators.

***

## Introduction

Understand the fundamentals before you build.

* [What is Blerify](/introduction/what-is-blerify.md) — the platform, the products, and who it's for
* [How It Works](/introduction/how-it-works.md) — the full issuance and verification flow from end to end

## Issuance

Issue verifiable credentials to your users.

* [Get Started](/introduction-to-issuance/get-started.md) — prerequisites and your first credential
* [Issue a Credential](/introduction-to-issuance/issue-a-credential.md) — step-by-step guide for Portal and API issuance
* [Issue an mDL](https://github.com/BlerifyPlatform/docs-public/blob/main/issuance/issue-an-mdl.md) — ISO 18013 mDoc issuance and PKI hierarchy
* [Portal Roles and Permissions](/introduction-to-issuance/portal-roles-and-permissions.md) — manage team access in the Issuance Portal

## ID Wallet

Integrate the Blerify Wallet into your mobile app.

* [Get Started](/id-wallet/get-started.md) — what the wallet is and how holders receive credentials
* [Mobile Integration](/id-wallet/mobile-integration.md) — iOS and Android integration guide

## Verification

Verify credentials presented by your users.

* [Get Started](/introduction-to-verification/get-started.md) — your first working verification integration
* [Verify a Credential](/introduction-to-verification/verify-a-credential.md) — session lifecycle, result schema, and error handling
* [Point of Verification](/introduction-to-verification/point-of-verification.md) — configure what to verify in the Portal
* [Biometric Binding](/introduction-to-verification/biometric-binding.md) — what key attestation proves and where the limits are
* [Platform Attestation](/introduction-to-verification/platform-attestation.md) — Android vs iOS evidence differences
* [OAuth Verification Flow](/introduction-to-verification/oauth-verification-flow.md) — redirect-based integration pattern
* [Portal Roles and Permissions](/introduction-to-verification/portal-roles-and-permissions.md) — manage team access in the Verification Portal

## Trust Registry

The trust infrastructure behind Blerify's credential guarantees.

* [Decentralized Root of Trust](/trust-registry/decentralized-root-of-trust.md) — how Blerify anchors trust without a central authority
* [DID Method](/trust-registry/did-method.md) — the `did:lac1` method specification
* [Assurance Tiers](/trust-registry/assurance-tiers.md) — what each tier guarantees and when to require it

## API Reference

Complete endpoint contracts and request/response schemas.

* [API Documentation](https://dev.blerify.com) — authentication and core API endpoints


---

# 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/welcome-to-blerify-docs.md?ask=<question>&goal=<endgoal>
```

`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.