Skip to content

Repository files navigation

NEUS Network — Portable Trust Infrastructure

NEUS Network social card

Portable Trust Infrastructure for Humans and AI.

Stop people and agents from the wrong action. Set what they may do, and check it before access, payment, or execution.

@neus/sdk on npm @neus/mcp-server on npm License Discussions NEUS verified portable proof

Why NEUS | Start building | Live surfaces | Support


Why NEUS

Every new app, agent, and partner usually starts from zero — no shared context about identity, ownership, or authority. NEUS turns those checks into portable proofs so people and AI keep context as they move, act under clear limits, and leave an audit trail behind.

A proof is something you already earned: who someone is, what they own, what they’re allowed to do. Put it on a profile, require it at a gate, or check it from your API — same proof, every surface.

Need What you get with NEUS
Stop re-proving the same facts in every product One portable proof apps and agents can reuse
Carry identity and ownership with the actor Profiles and ownership proofs that travel across gates
Authorize actions with clear limits Scoped permissions, current status, and enforce-before-act checks
Keep shared context for people and AI Live trust context in the editor, product, and API
Audit who did what — and under which authority Proof pages, stable references, and reviewable history
Ship trust without rebuilding each flow Hosted Verify, widgets, SDK, and MCP on one model

Start building

One command for assistants

Connect once. Your assistant carries your identity, trusted context, and scoped authority across editors — reusing what's verified, checking limits before sensitive actions, and leaving a proof for every result.

npx -y -p @neus/sdk neus setup
npx -y -p @neus/sdk neus doctor --live

Then ask your assistant:

Use NEUS so my identity, context, and authority travel with me. Reuse proofs when you can, verify when you must, and check authority before sensitive actions.

Path Next step
AI assistants (Cursor, Claude Code, Codex, VS Code) Install NEUS
MCP setup MCP setup · Hosted URL: https://mcp.neus.network/mcp
First app integration Quickstart
Reuse everywhere Integration guide
React gate VerifyGate
Server / API API overview
Agent trust Agents overview

Install neus-mcp from this repo's marketplace to connect Cursor in one click. See Install NEUS.

Add trust to an app

Drop in Hosted Verify, VerifyGate, or the SDK when your app needs portable trust — shared context at the gate, authority before access, proofs you can audit later.

Add trust to an agent

Give agents identity and scoped authority as proofs — so tools run under real limits, and every action stays auditable.


Live surfaces

Surface Use it for
Product Profiles, gates, and hosted product UX
Hosted Verify Browser verification for people and orgs
Proofs and results Portable records of identity, authority, and outcomes
SDK · @neus/sdk Issue, poll, and check proofs from your app
Widgets VerifyGate and ProofBadge for React products
API Server reads, checks, verifier catalog, and verification endpoints
Agents Agent identity, scoped authority, and audit-ready proofs
MCP Portable trust context in the editor — neus setup; registry metadata: @neus/mcp-server
Examples Runnable app and agent samples
Verifier catalog Live check IDs and inputs

Capability snapshot

The live verifier catalog is documented at docs.neus.network/verification/verifiers. JSON Schemas live in docs/verifiers/schemas/; the machine index is spec/VERIFIERS.json.

Capability Verifiers
Ownership and identity ownership-basic, ownership-social, ownership-dns-txt, ownership-org-oauth, ownership-pseudonym
Human and wallet trust proof-of-human, wallet-risk, wallet-link
Assets and contracts token-holding, nft-ownership, contract-ownership
Content and safety ai-content-moderation
Agent trust agent-identity, agent-delegation

This repository

Public docs, SDK (@neus/sdk), MCP registry package (@neus/mcp-server), widgets, examples, specs, and the neus-mcp editor plugin (install).

Open standard

Wallet-signed request envelopes follow the CAIP-380 (Portable Proof) ChainAgnostic draft. Their hash, DID binding, and signature can be checked without NEUS; verifier outcomes remain part of the NEUS portable proof. See the offline fixture and NEUS docs.

Support

Channel Use for
Docs Product and integration guidance
Changelog Release notes and upgrade paths
Platform status Maturity, beta scope, and upgrade expectations
Discussions Questions and implementation patterns
Issues Bugs and requests
SECURITY.md · dev@neus.network Vulnerability disclosure

License

  • SDK and tools: Apache-2.0
  • Smart contracts: BUSL-1.1 to Apache-2.0 in August 2028

About

The trust layer for people and AI. Portable identity, context, and authorization that travels.

Topics

Resources

Contributing

Security policy

Stars

24 stars

Watchers

2 watching

Forks

Releases

Packages

Used by

Contributors

Languages