> 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/learn.md).

# Learn

The Build guides show you how; these pages explain what you're actually getting. Read them when you're deciding which assurance tier to require, when a result contains a field you didn't expect, or when your compliance team asks what "verified" means here.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Assurance Tiers</strong></td><td>What Basic, Standard, and Premium each prove, and how to choose. Start here.</td><td><a href="/pages/97Z7jzVKbxvQOMFyEeZv">/pages/97Z7jzVKbxvQOMFyEeZv</a></td></tr><tr><td><strong>Biometric Binding</strong></td><td>The chain of evidence connecting the person in front of you to the person the credential was issued to.</td><td><a href="/pages/dTfmfY4enYIuzO1z4Z60">/pages/dTfmfY4enYIuzO1z4Z60</a></td></tr><tr><td><strong>Platform Attestation</strong></td><td>Why Android and iOS give you different evidence, and how to write a policy that handles both.</td><td><a href="/pages/COc1kYZxaF5wfggdFgGe">/pages/COc1kYZxaF5wfggdFgGe</a></td></tr><tr><td><strong>Verifier Trust</strong></td><td>How the user's wallet knows your verification request is really from you.</td><td><a href="/pages/Hyq1JzXrYkpj9q2H80AE">/pages/Hyq1JzXrYkpj9q2H80AE</a></td></tr></tbody></table>

## Next steps

[**Assurance Tiers**](/introduction-to-verification/learn/assurance-tiers.md) — the concept every other page in this section leans on.

See also: [Get Started](/introduction-to-verification/build/get-started.md) — when you're ready to stop reading and run one.


---

# 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/learn.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.