appId, credits, sponsors.
Users verify on neus.network. Your app sets returnUrl and builds the link with the SDK.
After completion: finish session with @neus/sdk, Authorization: Bearer on API calls. SDK Authentication
MCP: run neus_context first; tools return neus.network/verify links without requiring a key. Add Bearer with your personal access key from Access keys when you need a signed-in MCP session. MCP Auth
When to use
| Need | Why hosted |
|---|---|
| Login / signup | Guided signer |
| Social linking | OAuth in NEUS |
| Human / org checks | Interactive flows |
URL
Base:https://neus.network/verify
| Param | Role |
|---|---|
intent=login | Session-first login |
verifiers | Comma-separated IDs |
preset | Bundled verifier set |
gateId | Gate requirements |
returnUrl | Where to send the user next |
mode=popup | Popup + postMessage |
origin | Opener origin (popup) |
Auth surfaces
How hosted login behaves by environment (passkeys use WebAuthn in a secure context; a missing platform authenticator does not block cross-device or security-key prompts).| Surface | Passkeys | Wallet (AppKit / WalletConnect) |
|---|---|---|
| Desktop browser | Local passkey, phone handoff, or cross-device when the browser supports it | Connect Wallet from the page; QR and mobile flows need a normal user gesture |
| Mobile browser or installed PWA | Platform password manager or authenticator when available | Prefer the wallet app or the deep link the browser offers |
https, or http://localhost with an origin that matches your NEUS profile. Avoid raw LAN IPs.
PWA: service worker does not intercept /api/; do not cache auth traffic for hosted flows.
Code
mode: 'popup', origin: window.location.origin, then window.open. Listen for neus_checkout_done or neus_login_complete. Redirect: handle returnUrl and finish with the SDK.
Next
Authentication
Session token and Bearer.
Receipts
What to store after verify.