NEUS Network

One trust network for apps, agents, wallets, organizations & ecosystems.

Verification is the issuance lane. Receipts are the asset. Reuse is the value. Policy-backed action is the outcome.

Start building Explore the harness

trust-loop

VerifyIssue

ReceiptReuse

PolicyAction

Proofs are reusable trust receipts

Verify

Connect verifiers to attest identity, ownership, humanity, or compliance.

Issue receipt

Every verification mints a portable, policy-readable receipt with a qHash.

Reuse

Present the same receipt across apps, agents, wallets, and marketplaces.

Policy action

Gates and workflows enforce trust-backed outcomes without repeated checks.

Set up the universal harness

Install the SDK and run the project bootstrap.

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

Add portable skills to Claude Desktop or any MCP host.

mkdir -p ~/.claude/skills/neus/[[SKILL.md](http://SKILL.md)]([http://SKILL.md](http://SKILL.md)) # Twelve-tool public MCP surface: proofs, agents, secrets, jobs, trust graph, etc.

Every push must pass the build gate before deployment.

npm run type-check npm run build

Interface showcase

Trust Graph

Animated node-link graph of agents, proofs, and verifiers.

Jobs Dashboard

analyze-depsrunning

deploy-previewdone

Status badges, run IDs, and recurrence indicators at a glance.

Secrets Vault

OPENROUTER_KEY••••••

NEUS_MCP_KEY••••••

AES-256-GCM encrypted aliases, never exposed in prompts.

Agent Delegation

neus-dev

code release audit

0x4a3b…9c21

Proof Receipt

qHash

0x7f8a9b…e4d2c1

ownership-basic eip155

2026-06-16 · hub + base

Verifier Catalog

ownership-dns-txtdomain

proof-of-humanidentity

agent-delegationagent

Quick start

Bootstrap

Run npx -y -p @neus/sdk neus setup and authenticate.

Create your first proof

Pick a verifier, complete the check, and receive a qHash receipt.

Attach an agent

Delegate an agent wallet, bind skills, and mount secrets.

Run a job

Queue or schedule work, watch the live output panel, and archive receipts.

FAQ

A signed, verifiable record produced by a NEUS verifier. It includes a qHash, timestamp, and chain metadata, and can be reused by any app or agent that accepts NEUS proofs.

Yes. NEUS uses an ORG controller wallet plus optional shared AGENT wallets for delegation. Wallet connection is handled via AppKit.

Absolutely. The SDK CLI, local MCP servers, and IDE runtime gates are designed for local-first development with Vercel deployment as a gate.