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.

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: Palm OAuth2 for app-scoped identity, Palm SDK for mobile-first flows, or Palm ZK Proof when the product requires anonymity.
• Your system receives: an app-scoped identifier, a verification result, or a ZK proof depending on the chosen path.

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's dedicated Liveness Detection SDK — a separate SDK from the Palm SDK used for palm verification.
• Your system receives: a pass/fail result, without needing to process raw biometric data or handle a signed token.

Agent Verification (AG9)

Use AG9 when a third party needs to trust that an autonomous AI agent is controlled by a real, verified human — not a bot farm or malicious actor.

• Best for: agent marketplaces, autonomous-agent platforms, and any system granting agents privileges that should trace back to a real person.
• Integration path: AG9, which binds an agent's Ed25519 key to a human who has passed VeryAI palm verification.
• Your system receives: a public verification endpoint to confirm an agent is registered and owned by a verified human.

Discord Verification Bot

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.

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