Skip to main content
NEUS issues one portable proof receipt per completed verification. Save the proof receipt ID as proofId and use it for checks, gates, widgets, and /proof links rather than treating raw signatures as the long-lived record. The same receipt ties hub profile, access gates, and agent flows together—fund credits and (when you sponsor users) sponsor grants from Get started so billing matches your product.

How it works

Verification: verify once, then Proof ID as verified proof receipt, then reusable proof across apps, agents, and APIs

Start here

Pick one row—then follow Integration (check → verify → save → reuse).
You are…Start here
Shipping a product (attribution + credits)Get started — hub, appId, who pays
First proof in code (local try)Quickstart — return to Get started before production
No wallet / guided login in browserHosted Verify
React gate or badgeWidgets
Cursor / Claude / VS CodeMCP
UnsureChoose a path
Assistants: LLM docs.

What you can build

Use caseVerifier
Human-only signup or accessproof-of-human
Token / NFT gated productsnft-ownership · token-holding
Verified creator or org badgesownership-basic · ownership-org-oauth
Proof-backed content and postsownership-basic
Agent identity and delegationagent-identity · agent-delegation
Domain-verified organizationsownership-dns-txt
Full verifier catalog →

URLs

WhatURL
Hosted verificationhttps://neus.network/verify
Platformhttps://neus.network/hub
APIhttps://api.neus.network
MCPhttps://mcp.neus.network/mcp

Examples

React, Node.js, curl → · LLM / assistant index →