SDKs and a REST API
Python, Android and iOS SDKs plus a REST API — enroll, generate, sign, and verify against a live biometric, with the same primitive underneath.
Explore public documentation for Python, Android and iOS SDKs plus a REST API. This is implemented cryptography you can inspect. Review the implementation before you speak to sales.
# Enrollment — capture stays on-device; # only a SensePrint is sent POST /v1/enroll { "sense_print": "<encrypted, revocable>" } # Generate a per-purpose keypair from a live capture, # then sign (illustrative; capture handling is set out in the docs) POST /v1/sign { "challenge": "<nonce>", "capture": "<on-device>" } # → { "signature": "...", "alg": "ML-DSA" } # the key has ceased to exist # Verify with a prepared supported verifier — # including offline POST /v1/verify { "credential": "<sense_print>", "signature": "..." } # → { "valid": true } # same call against the hosted API # or your own deployment
from sensecrypt import Client c = Client(api_key=...) # Enrollment returns only a revocable SensePrint sp = c.enroll(capture=on_device_capture()) # Generate from a live capture, sign, discard — # no key at rest sig = c.sign(challenge, capture=on_device_capture()) assert c.verify(credential=sp, signature=sig) # generated signing key discarded; # enrollment artifacts may persist
import SenseCrypt let c = SenseCryptClient(apiKey: apiKey) // returns a SensePrint only let sp = try c.enroll(capture: capture) // key generated, used, discarded let sig = try c.sign(challenge, capture: live) // verifies offline with a prepared // supported verifier let ok = try c.verify(credential: sp, signature: sig) // FIPS 203 / 204 live in PKI — // see the whitepapers
Illustrative flow — the key that never stays at rest is the signing key generated from the live face. The docs cover the production SDK surface; supported algorithms depend on the product. The post-quantum scope and its named classical exceptions are set out in the whitepaper Never build the biometric database.
Integrating an identity provider? IdP retains encrypted tenant signing keys and uses classical ES256 for OIDC federation. SAML uses separate RSA signing keys. SenseCrypt IdP supports FAPI 2.0, FAPI 2.0 Message Signing and FAPI-CIBA for financial-grade flows. The OIDC and SAML pages cover their separate protocol interfaces.
Python, Android and iOS SDKs plus a REST API — enroll, generate, sign, and verify against a live biometric, with the same primitive underneath.
Run verification in your infrastructure. The developer docs explain the deployment requirements.
Review the API references and bring your technical questions to our engineers.