Skip to main content
Every NEUS integration follows the same loop.
StepDo this
1Check whether you already have a valid receipt
2Verify only when the receipt is missing, stale, or needs a new trust decision
3Save the returned qHash on your user, account, agent, or record
4Reuse the receipt before access, payment, delegation, or action

​
Where code runs

LayerUse
BrowserVerifyGate, getHostedCheckoutUrl, hosted /verify
ServergateCheck with gateId
AssistantHosted NEUS MCP, neus_context, neus_proofs_check, neus_agent_link
Passkey, wallet, and OAuth flows should run on NEUS hosted pages by default. Do not ship access keys or server secrets in browser bundles. Backend receipt creation and access keys: Integrations.

​
Integration options

Hosted Verify

Browser flow owned by NEUS.

SDK

JavaScript helpers for app and server flows.

VerifyGate

React access gates.

Agents

Agent identity and delegation.
Identity and chain terms: CAIP-380 Portable Proof. Receipt fields and URLs: Receipts and results. Next: Hosted Verify
Last modified on June 4, 2026