Skip to main content
Product flow (diagram): Overview → How it works. This page names terms, verifier types, and what you get in responses.

​
Loop

Check ──▶ Verify (if needed) ──▶ Save ──▶ Reuse
  1. Check: existing proofId still satisfies policy?
  2. Verify: if not, run a flow (hosted, SDK, or API)
  3. Save: proof receipt ID on the user or record
  4. Reuse: gates, proof pages, agents, MCP—without re-verifying

​
Outcomes

OutcomeExamples
IdentityLogin, social linking, team verification
OwnershipContent provenance, file receipts, authorship
AccessNFT gating, token thresholds, premium content
Abuse PreventionHuman verification, wallet safety
AgentsAgent registration, scoped delegation

​
Types

TypeBehaviorExamples
InstantWallet signs, proof createdownership-basic, agent-identity
InteractiveUser completes hosted flowsocial linking, human verification
LookupCheck against live stateNFT ownership, token balance

​
Terms

TermMeaning
Proof receipt IDStable identifier for a proof, exposed as proofId in SDK responses (same value as qHash on the wire). See Proof receipts.
VerifierThe capability being verified
Signing stringThe message the wallet signs
Hosted verifyNEUS-hosted UI at /verify
Every verifier starts in one of two ways: direct-sign receipt (wallet or server signing) or Hosted Verify (interactive). Visibility modes: Security and trust.

​
Response

  • proofId
  • status · verified · processing · failed
  • Page · https://neus.network/proof/[proof-id]

​
Next

Verifiers

Pick capability.

How it works

Flow detail.

Signing

Messages.

Lifecycle

Poll + revoke.