Use neus_verify to create a receipt when the signed-in account can complete the check in-session. For steps that need a browser (OAuth, personhood, payment, wallet connect), use neus_verify_or_guide instead — it returns a hosted link.
Always run neus_proofs_check first and reuse an existing receipt before creating a new one.
When signed in, omit walletAddress — the tool uses your profile account from neus_context.
Signing flow
neus_verify is two-phase when a signature is required. The first call returns the exact signing material once; complete it with the bound account and submit it back to finalize. Do not restart the preparation step blindly — finalize with the material you were given.
Output
A plain-language Passed, Action needed, or Blocked result. On success, the tool also returns the receipt ID in qHash for your server. If a browser step is required, it returns a next_action link.
Prefer verify-or-guide for most assistants: neus_verify_or_guide. Last modified on July 13, 2026
