Skip to main content
Alentra is in private beta. Google Sandbox exercises the real encrypted wallet path with fictional Utopia credentials. Every production country/profile/provider route stays coming soon until verifier/issuer enrollment, trust, acceptance, and Alentra approval.
Alentra turns a government-issued credential in a user’s digital wallet into a verified result your app can trust: their name, that they’re over 21, or a device signature tied to your document and retained evidence. You never build a wallet-verification stack or touch a wallet SDK. You publish the ordered flow once as a workflow, create a fresh session from its id, hand the user a link, and receive a signed webhook when their wallet completes it. For sign, Alentra stores the exact uploaded originals as immutable evidence after completion.

Start here

What is Alentra?

The model in two minutes: primitives, wallets, and sessions.

Quickstart

Publish a workflow, create its first run, and receive a verified result.

Workflows

Reusable definitions, launch modes, revisions, and run-specific data.

Primitives

identify, age_verify, light_sign, sign — and how to chain them.

API Reference

Every endpoint, request, and response.

What you can build

Identity verification

Government-attested name, date of birth, country, and document number — no photographed-ID upload, OCR, or liveness vendor.

Business-redacted age gates

Prove a user is over 18 or 21. The age result contains only true/false and the threshold, not the birth date; Alentra retains the encrypted underlying evidence.

Document signatures

A device signature bound to a verified identity, with the original signed bytes and an independently checkable audit reference.

Terms acceptance

A lightweight signature over short inline terms — consent you can prove later.

Why it’s different

Government-attested

Claims come from a real issuing authority’s signed credential and are verified cryptographically — not self-asserted, not OCR’d.

Composable

Compose identify, age_verify, and sign into one session. The user completes them in one flow; you get one webhook per step.

Pay per result

You’re charged only for steps that successfully verify — from $0.05. There is no subscription; self-serve accounts fund their balance manually.