Skip to main content
Default: users complete checks on neus.network/verify. Your server runs gateCheck with your published gateId. No wallet code in your app, and no NEUS account required for end users.
NeedMechanismWallet code in your app
Product verification (default)VerifyGate / Hosted Verify + gateIdNo
MCP client authOAuth 2.0 + PKCENo
Server automation as your profileBearer npk_* access keyNo
Server creates receipts for an approved userApp link + verifyFromAppNo
Sign inside your pageSDK verify + walletYes — rare
Server integration: Integrations.

Hosted Verify (default)

https://neus.network/verifyHosted Verify. Send users to your checkout with gateId; the enforcement policy bills your Hub credits.

MCP OAuth

MCP clients (Claude Code, OpenAI, VS Code, Cursor) authenticate via OAuth 2.0 Authorization Code with PKCE:
npx -y -p @neus/sdk neus setup
npx -y -p @neus/sdk neus auth
See MCP OAuth.

Profile access keys

Access keys for servers, CI, and MCP automation. Never in browser bundles.

Backend receipts

For backend-created receipts after a user approves your product once, see Integrations. Separate from publishing a gate in Hub, which bills hosted checks to your account.

Signing inside your app

Signing format · signMessage from @neus/sdk

Raw HTTP

POST /api/v1/verification/standardize → sign signerStringPOST /api/v1/verification. Signing format. MCP Auth · SDK Authentication
Last modified on June 4, 2026