Skip to main content
The repository (veriqa.app/source) carries a gallery of samples under samples/. Everything there is MIT-licensed and written to be lifted into your own project.
Veriqa lives on the issuer side. An application that only signs users in stays a plain OpenID Connect relying party — no Veriqa package, no SDK. Veriqa packages appear only where the application is the issuer (embedded) or calls the confirmation API server-to-server.
Samples come in two forms:
  • Runnable — projects with their own README.md, ports and configuration. Start a .NET sample with dotnet run --project <path>; the samples outside .NET that run next to Veriqa are started with docker compose up in their folder.
  • Code to copy — one file per stack with the complete client wiring. There is no project file around it: the surrounding application is yours.

Sign-in and confirmation

Sign-in on a website via a messaging app

The issuer with Veriqa embedded, a stock OIDC client, the same sign-in under .NET Aspire and the client code for Java, Node and Python.

Step-up, second factor, human-in-the-loop

A backend asks a person to confirm an action: a plain confirmation, step-up before a destructive action and approval of an AI agent’s tool call.

Showcase samples

Showcases imitate a whole product, so the flows can be seen end to end the way a user encounters them.

Nova Stream sample — TV sign-in emulator

Sign-in by QR code from the sofa, a date of birth and a favorite genre collected inside the sign-in, and step-up when buying a title; written for TV browsers.

Helio sample — customer support

A public support page, a sign-in that asks for no contact details, a verified phone number and email collected when they are needed, and step-up before a ticket is closed or deleted.

Agent action approvals

A Claude Code plugin: selected agent actions wait until a person approves them in the messaging app.

Channel and deployment samples

The custom-channel host and the Aspire sign-in sample share port 7320 — run them one at a time. In dotnet/pseudo-channels, a provider is enabled by its OAuth client credentials (a non-empty ClientId), not by a channel’s Enabled flag and a bot token; the sample’s README covers the setup.

Running the .NET samples

  • .NET SDK 10.0+ and a trusted local HTTPS certificate (dotnet dev-certs https --trust).
  • Enable at least one channel and give it credentials. Every sample ships with all channels "Enabled": false; with none enabled the sign-in page returns no_channels_available. A bot token is the quickest route — see Channel setup and the sample’s own README.
  • In pairs such as login + login-client, start the issuer first: the client fails discovery otherwise.