KEYRA

Stripe-level clarity

Integrate human authorization in minutes.

SDK docs, API playground, and sample integrations for WebAuthn + challenge-response approvals.

  • JS/TS, Python, Go quickstarts
  • Challenge lifecycle: request → verify → attest → sign
  • Production-safe patterns for AI approvals
Open docs
Network radiating from KEYRA

Challenge lifecycle

Request → verify → attest → sign.

Every integration follows the same human-in-the-loop pattern — whether you are building passkey login, AI approvals, or physical access.

01 · Request

An app, AI agent, or lock issues a cryptographic challenge — never a password field.

02 · Verify

You touch KEYRA ONE. Biometric proof is checked locally in milliseconds.

03 · Attest

The secure element signs a response bound to the challenge — no replay possible.

04 · Sign

The relying party receives hardware-rooted proof that a human authorized the action.

See the user flow →

Integration patterns

Built for real production flows.

WebAuthn & passkeys

Hardware-bound credentials with FIDO2-aligned flows — biometrics never leave KEYRA ONE.

AI agent approvals

Sign agent-initiated actions with explicit human proof before funds move or data is released.

BLE challenge-response

Low-latency attestation for physical access, device pairing, and high-trust mobile flows.

API design

Predictable. Auditable. Human-first.

  • Challenges are single-use and time-bound
  • Attestation payloads are verified server-side with device certificates
  • No biometric templates are transmitted to your backend
  • Webhooks notify your system when a human authorizes or rejects

Example · create challenge

POST /v1/challenges
{
  "action": "transfer.approve",
  "amount": 12500,
  "currency": "USD",
  "userId": "usr_8f2a"
}

→ 201 { "challengeId": "chl_...", "expiresAt": "..." }