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.
| Need | Mechanism | Wallet code in your app |
|---|
| Product verification (default) | VerifyGate / Hosted Verify + gateId | No |
| MCP client auth | OAuth 2.0 + PKCE | No |
| Server automation as your profile | Bearer npk_* access key | No |
| Server creates receipts for an approved user | App link + verifyFromApp | No |
| Sign inside your page | SDK verify + wallet | Yes — rare |
Server integration: Integrations.
Hosted Verify (default)
https://neus.network/verify — Hosted 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 signerString → POST /api/v1/verification. Signing format.
MCP Auth · SDK Authentication Last modified on June 4, 2026