Build human verification into your workflow

Choose the processing model that fits your application: hosted API matching, private Edge evaluation, or a mobile verification handoff.

Choose your integration path

Start with your runtime and where biometric data can be processed.

@biotone/sdk · Apache-2.0

Hosted API + public SDK

Use typed API clients and capture components to integrate verification into your product. Matching runs on the BioTone API; review upload, storage, and retention requirements for your tenant.

Read the API documentation →

@biotone/edge · Approved partners

Private Edge SDK

Evaluate local biometric processing, encrypted templates, and distributed-key workflows with the private Edge SDK. Access and supported platforms are agreed for your pilot.

Request evaluation access →

QR code or deep link

Mobile authentication broker

Hand a browser or kiosk session to the mobile verifier. Your backend validates the result and connects it to your identity provider and application authorization rules.

Start with the Quickstart →

From sandbox to pilot

Validate one complete flow.

Use the SDK package and documentation supplied for your tenant. Complete one enrollment-to-verification flow on the devices you plan to support.

1. Establish the tenant and data boundary

Confirm API access, package entitlement, processing location, consent, and retention before capturing biometric data.

2. Enroll, verify, and handle failure

Test your chosen signals with real devices. Exercise rejected captures, failed matches, expired sessions, and user cancellation.

3. Enforce authorization in your backend

Validate the verification result and its session context. Apply your own access policy, audit the decision, and test revocation and recovery.

Distributed Living Key evaluation

Evaluate distributed operations using separate keystore participants and the person’s key share. Test a complete approval, unavailable nodes, and recovery before rollout.

If the person will use a hardware token, include that token and host device in the acceptance test.

Identity provider integration

Bring your identity provider and target sign-in flow. We will confirm configuration and complete an end-to-end test before rollout.

Compare deployment modes → · Review security boundaries →

Bring your runtime and one use case.

Tell us where capture happens, where matching may run, and which action needs verification.