Skip to main content
The JavaScript SDK does four things: build hosted verify URLs, create receipts, poll status, and run server-side gate checks. Use as much or as little as you need — a hosted link and a server check are enough for most apps. MCP calls the same APIs: MCP.

Default placement

Avoid credentialed fetch to api.neus.network from the browser; use SDK helpers or your backend.

Browser (default)

Hosted sign-in and checks on NEUS:
React: VerifyGate from @neus/sdk/widgetsQuickstart. After you have a receipt ID (qHash), optional wait: NeusClient + pollProofStatusVerifications.

In-app signing (optional)

client.verify({ wallet: ... }) only if signing stays in your page. Pass the wallet/provider explicitly. Non-EVM signing also needs chain as CAIP-2. CAIP-380 Portable Proof · Signing format.

Eligibility on your server

API mapping

Optional: timeout on NeusClient.

Defaults

client.verify() defaults private. Security. VerifyGate create also defaults private. Security and trust

Next

JavaScript

Client setup and common methods.

Verifications

Create, poll, and read receipts.

Authentication

Access keys and server auth.
Last modified on July 13, 2026