Products & Use Cases

Start with the product experience you want to ship, then choose the integration path that gives your app the right amount of identity, privacy, and implementation control.

Discord bot verification

Use VeryAI to verify members before assigning roles, unlocking channels, or allowing campaign participation in a Discord community.

• Best for: communities, gated groups, campaign access, and reputation-sensitive servers.
• Integration path: Very-fier Discord bot.
• Your system receives: a role or access decision after the user completes verification.

Liveness detection

Use liveness detection when your product needs to know that a capture came from a live person, not a replay, static image, or spoof attempt.

• Best for: fraud prevention, account recovery, onboarding checks, and step-up verification.
• Integration path: VeryAI Native SDK or a VeryAI-hosted verification flow, depending on the product surface.
• Your system receives: a liveness or verification outcome, without needing to process raw biometric data.

Palm verification

Use palm verification when you need to confirm that the user is the same enrolled person or is associated with a specific account.

• Best for: re-verification, rewards, login, fraud-resistant account linking, and identity continuity.
• Integration path: OAuth2 for app-scoped identity, Native SDK for mobile-first flows, or ZK when the product requires anonymity.
• Your system receives: an app-scoped identifier, a verification result, or a ZK proof depending on the chosen path.

OAuth / native SDK

Use OAuth or native SDK integrations when you need a persistent product relationship with the user.

• OAuth2: standard browser flow that returns app-scoped tokens and an external user ID.
• Native SDK: mobile-first flow for apps that need tighter control over capture, liveness, or UX.
• Best for: login, account linking, rewards, support, and re-verification.

ZK proofs

Use ZK proofs when your application needs to verify eligibility or uniqueness without receiving a persistent identity.

• Best for: anonymous voting, private eligibility checks, Web3 gating, and one-person-one-action flows.
• Integration path: ZK Integration.
• Your system receives: a zero-knowledge proof bound to your verification context.

Decision guide