proofId / qHash). Persist it in your product. Use that ID for checks, gates, widgets, and /proof links—not raw signatures.
How it works
Quickstart
~5 min, first proof (no app id required).
Get started
Hub, app id, credits, billing—before production.
Choose your path
Hosted, widgets, SDK, API, or MCP.
Lowest-friction order
Do this sequence to avoid billing surprises and rework:- Hub — sign in with passkey or wallet; review Credits and Apps when you are close to shipping.
- Get started — real traffic:
appId, who pays, credits, sponsor vs self-pay. - Choose your path — pick Hosted Verify, widgets, SDK, API, or MCP for your UX.
- Integration — production loop: check → verify → save → reuse.
What you can build
| Use case | Verifier |
|---|---|
| Human-only signup or access | proof-of-human |
| Token / NFT gated products | nft-ownership · token-holding |
| Verified creator or org badges | ownership-basic · ownership-org-oauth |
| Proof-backed content and posts | ownership-basic |
| Agent identity and delegation | agent-identity · agent-delegation |
| Domain-verified organizations | ownership-dns-txt |
Choose your path
| Path | Best for | Effort |
|---|---|---|
| Hosted Verify | Guided login | Redirect or popup |
| Widgets | React gates | <VerifyGate> |
| SDK | Custom | Full control |
| API | Server-side checks | HTTP |
| MCP | AI agents | https://mcp.neus.network/mcp |
URLs
| What | URL |
|---|---|
| Hosted verification | https://neus.network/verify |
| Platform | https://neus.network/hub |
| API | https://api.neus.network |
| MCP | https://mcp.neus.network/mcp |
Examples
React, Node.js, curl → · AI assistant doc exports (llms.txt) →