Seventh Sense

Explore the docs.
Start building.

PythonRESTAndroidiOS

Explore public documentation and SDKs for Python, REST, Android and iOS. This is implemented cryptography you can inspect. Review the implementation before you speak to sales.

The shape of an integration

Enroll. Derive. Sign. Verify.
The key never stays at rest.

SenseCrypt / IntegrationIllustrative flow
# Enrollment — capture stays on-device;
# only a SensePrint is sent
POST /v1/enroll
  { "sense_print": "<encrypted, revocable>" }

# Derive a per-purpose keypair from a live capture,
# then sign
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

Illustrative flow — the key that never stays at rest is the face-derived signing key. The docs cover the production SDK surface; supported algorithms depend on the product. The post-quantum design and its named exceptions are specified in the architecture whitepaper — this page never routes you to the docs for post-quantum claims.

Integrating an identity provider? IdP uses classical ES256 for OIDC federation, and 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.

Built for your environment

Build SenseCrypt into your infrastructure.

01

Native SDKs

Python, REST, and native mobile (Android & iOS) — enroll, derive, sign, and verify against a live biometric, with the same primitive underneath.

02

Verify on your infrastructure

Run verification in your infrastructure. The developer docs explain the deployment requirements.

03

Evaluate before you integrate

Review the API references and bring your technical questions to our engineers.