Start here
Building a product? Get started — platform profile, link app, credits,appId, sponsor grants, then choose an integration path.
Choosing an integration path? Choose an integration path — Hosted Verify, Widgets, SDK, API, or MCP.
How it works
- Verify — User completes verification (hosted UI, wallet, or social).
- Save — You store the proof receipt ID.
- Reuse — Same proof for login, gating, policy, and agents.
Get started
Builders: platform, app link, billing, first integration.
Choose your path
Pick Hosted Verify, Widgets, SDK, API, or MCP.
Quickstart
First proof with the SDK (code).
Hosted Verify
No custom verification UI — redirect or popup.
Verifier catalog
What you can verify.
Billing
Who pays — deep reference.
Integration paths
| Path | Best for |
|---|---|
| Hosted Verify | Login, guided verification, least UI work |
| Widgets | React gating and badges |
| SDK | Custom browser or server flows |
| API | HTTP from your servers |
| MCP | Cursor, Claude, agents — browser links first |
URLs you’ll use
| What | URL |
|---|---|
| Hosted verification | https://neus.network/verify |
Platform (/hub) | https://neus.network/hub |
| API | https://api.neus.network |
| MCP | https://mcp.neus.network/mcp |