neus.network/verify) runs sign-in and trust checks in the browser. Your app embeds a gate or redirects users to NEUS; your server confirms with gateCheck. No wallet or passkey code in your app. End users do not need a NEUS account unless your flow requires it.
Credits apply to trust checks and saved receipts, not to hosted session sign-in. See Trust stack · Pricing.
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: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 creating a portal under profile → Portals, 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