What Happens
The user or wallet completes the needed action
That can be a wallet signature, a hosted account link, a human-verification step, or a lookup against live state.
NEUS runs the verification
Some verifiers finish immediately. Others complete asynchronously and need a status check.
Main Flow Types
| Mode | Use case | Notes |
|---|---|---|
| Hosted verify | Guided login and interactive verification | Standard path for social accounts, team checks, and human verification |
| SDK verification | Browser or server product flows | Direct control over verification requests |
| Raw HTTP verification | Advanced or server-owned integrations | Use only when you need direct API control |
| Hosted interactive verification | OAuth, human proof, social flows | Widgets and MCP will hand off to hosted verify automatically |
| Gate checks | Server-side policy decisions | Use GET /api/v1/proofs/check for minimal yes/no eligibility |
What You Get Back
- A verification response that can include status data
- A hosted verify handoff for interactive flows
- A pollable status endpoint for asynchronous verifiers
- A reusable proof receipt ID
Related
Verification Lifecycle
Statuses, polling, reuse, and revocation.
Signing Format
Hosted, SDK, and advanced signing guidance.
Verifier Catalog
Choose the right verification capability.
API Overview
HTTP endpoints and advanced API usage.