> 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-to-verification/verification.md). # Introduction to Verification Blerify's verification product is the **Universal Point of Verification — UPoV**: one integration through which your business obtains verified information from credential holders. It answers one question: **can I trust the credential this person is showing me?** When someone presents a digital credential on your website or in your app, UPoV checks that it's genuine, that its issuer hasn't revoked it, and that it belongs to the person presenting it — not to someone else. You get a clear answer in seconds. For the person being verified, it feels simple: they tap a button or scan a QR code, their digital wallet shows them exactly what you're asking to see, and they approve with their fingerprint or face. No forms to fill in, no documents to photograph, no waiting for a review. For your team, the work splits in two. Someone configures a **verification rule** in the [Blerify Portal](https://portal.blerify.com/) — a point-and-click setup where you choose which credential to accept and which details to request; no code involved. Then a developer connects your system to Blerify with two simple calls. Nobody on your side has to understand cryptography: Blerify runs the checks and reports the facts. Everything in this section falls into one of four parts. If you want to see the product applied to a real scenario before deciding anything, read a **Use Case** — no technical background needed. Developers here to ship start with **Build**. **Learn** explains what the checks actually prove, and **Reference** is for lookup.


🛠️ Build	Task-oriented guides: run your first verification, create a rule, read the result.	/pages/EdpyN7bY1v9XGXoA0VcZ
💡 Use Cases	Complete scenarios — age checks, customer onboarding — showing which decisions to make and why.	/pages/aESvKqCUjU3NmUsB4uTv
📘 Learn	The concepts underneath: assurance tiers, biometric binding, platform attestation, verifier trust.	/pages/gIdnTgzdp1JQPdsSfXnt
📗 Reference	Exact contracts: the API, verification rule configuration, portal roles, and a working demo app.	/pages/aUvfEEJGi6hru5yfCLn1

{% hint style="info" %} **First time here?** Start with [Create a Verification Rule](/introduction-to-verification/build/create-a-verification-rule.md) — everything begins with the rule you configure in the Portal. Then run your first verification against it in [Get Started](/introduction-to-verification/build/get-started.md). {% endhint %} ## Next steps [**Create a Verification Rule**](/introduction-to-verification/build/create-a-verification-rule.md) — the Portal setup every verification starts from. See also: [Age Verification](/introduction-to-verification/use-cases/age-verification.md) — a complete scenario in five minutes of reading · [Assurance Tiers](/introduction-to-verification/learn/assurance-tiers.md) — how much proof each tier gives you. --- # 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-to-verification/verification.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.