Choose an Integration Path
NEUS supports four primary integration surfaces. Start with the surface that matches your product constraints, then expand into additional surfaces as your trust model evolves.Pick by job to be done
Ship a browser or app flow
Use the JavaScript SDK when you need proof creation, status polling, hosted verify handoff, or private proof access in a custom UI.
Gate content quickly
Use Widgets when you want the fastest hosted or embedded path with React components and script-tag badge rendering.
Integrate AI or agent tooling
Use the MCP server when an AI client needs verifier lookup, gate checks, or a hosted verify handoff without reimplementing backend logic.
Go deeper on backend policy
Use the HTTP API when your backend needs gate checks, verifier catalog reads, auth code exchange, or explicit status polling.
Recommended journey
Start with reader intent
Decide whether you need onboarding, access gating, proof issuance, hosted checkout, or agent-facing trust signals.
Choose the thinnest viable surface
Prefer Widgets for the fastest launch, the SDK for custom UX, the API for backend policy, and MCP for AI-native integrations.
Keep `/verify` as the canonical hosted path
Interactive flows should converge on the hosted verify surface instead of inventing parallel auth or checkout routes.
Which path should you choose?
| If you need… | Start here | Then add |
|---|---|---|
| Fastest production launch | Widgets | SDK for custom UX |
| Custom browser UX | SDK | API for backend checks |
| Backend-only eligibility decisions | API | Cookbook for rollout patterns |
| AI assistant or agent workflows | MCP | Agents for proof models |
| Org/app onboarding and sponsored flows | Hub Integrator Setup | Auth + Hosted Verify |