> ## Documentation Index
> Fetch the complete documentation index at: https://veriqa.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# All use cases

> Every Veriqa use case in one table: what each one gives you, which mechanism it is built on, and whether we ran it ourselves or you can build it on the current version.

The table lists every use case covered in the documentation, with the mechanism it is built on and
its status:

* **We ran it** — we have run this use case ourselves; the cell links to a sample or a video.
* **Works on the current version** — Veriqa already has everything the use case needs, but we have
  no ready-made sample for it. Some of these you build yourself from the existing mechanisms; the
  use case page says so.

| Use case | What it gives you | Mechanism | Status |
| - | - | - | - |
| [Passwordless sign-in and registration](/docs/scenarios/passwordless-login) | A QR code or a button instead of a password; a new user signs up with the same action | Sign-in | We ran it: [sample](/docs/samples/sign-in), [video](/docs/videos/web-sign-in) |
| [Sign-in and channel linking](/docs/scenarios/channel-linking) | The user is signed in, and your product gets a channel for notifications | Sign-in; a server-to-server transaction where there is no redirect | We ran it: the `samples/dotnet/inproc/confirmation` sample |
| [Second factor and step-up](/docs/scenarios/step-up) | A fresh confirmation before a sensitive operation | A repeated sign-in with an `auth_time` check; to confirm an action, a server-to-server transaction with `expected_identities` | We ran it: [sample](/docs/samples/confirmation), [video](/docs/videos/desktop-step-up) |
| [Replacing SMS codes](/docs/scenarios/sms-replacement) | The same flow without paying for every message | Sign-in | Works on the current version |
| [Leads and feedback without CAPTCHA](/docs/scenarios/lead-capture) | A confirmed contact instead of an address typed by hand | Sign-in without opening a session | We ran it: [confirmed form submission](/docs/integrations/confirmed-form) on the Telegram channel |
| [Account recovery](/docs/scenarios/account-recovery) | A linked channel instead of a chain of emails and codes | Sign-in through a linked channel | Works on the current version |
| [Sign-in surfaces](/docs/scenarios/surfaces) | Sign-in on a computer, a phone, a TV and a kiosk | Sign-in; a server-to-server transaction where there is no browser | We ran it: videos [on a desktop](/docs/videos/desktop-sign-in), [on a phone](/docs/videos/mobile-sign-in), [on a TV](/docs/videos/tv-sign-in) |
| [Smart TV and keyboard-free surfaces](/docs/scenarios/smart-tv) | Sign-in where there is nothing to type on | Sign-in; a server-to-server transaction exchanged for an `id_token` | We ran it: [Nova Stream](/docs/samples/showcase/streaming-tv) |
| [Approving AI-agent actions](/docs/scenarios/agent-approvals) | A risky agent step runs only after a person agrees | Server-to-server transaction | We ran it: the `samples/dotnet/inproc/agent-approval` sample, the [Claude Code mod](/docs/samples/showcase/claude-code) |
| [Place and identity](/docs/scenarios/place-and-identity) | Confirmation that the person is in the room | Server-to-server transaction | Works on the current version; you build it |
| [Stronger sign-in with a chain of channels](/docs/scenarios/auth-chain) | The sign-in is confirmed in several channels | Sign-in in several channels | Works on the current version; you build it |
| [Resilience to a personal-data leak](/docs/scenarios/leak-resilience) | Your database holds no identifiers that lead back to a person | Channel identity store | Works on the current version; you build it |
| [Honest voting on any website](/docs/scenarios/honest-voting) | Each vote is confirmed in the voter's messenger | Server-to-server transaction | Works on the current version; you build it |

To choose the mechanism for your task, see [Basic scenarios](/docs/basic-scenarios); the authorize
parameters for the sign-in use cases are in [Integration scenarios](/docs/guides/scenarios).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.