Skip to main content
Portable Proof carries verified identity, authority, and action evidence across apps, agents, and networks. NEUS provides the hosted infrastructure to create, verify, enforce, and audit those proofs. Keep your current sign-in, identity provider, payment stack, model, and agent framework. The receiving product owns the decision and enforces it. Choose the shortest integration path for the decision your product already needs to make.

Connect an assistant

Add the hosted MCP endpoint, sign in, then protect an action.

Add Hosted Verify

Use hosted sign-in, then confirm the result on your server.

Sell protected access

Publish the checks and price once. Add one component to your app.
Sign-ups. Markets. Payouts. Partners. The same check-before-action flow works across each one.

​
Connect an AI assistant

The portable trust harness for AI. Add the hosted MCP endpoint, click Connect, and the same profile, checks, Portable Proofs, permissions, and private context are available in that client. https://mcp.neus.network/mcp Then ask:
Before you take a sensitive action, use NEUS. Reuse what I already have.
NEUS answers Passed, Action needed, or Blocked. You now have a clear decision before the action runs. Continue with MCP setup and the NEUS trust stack for MCP.

​
Add a check to an app

Keep your sign-in. Send visitors to NEUS for the check, then confirm on your server. Hosted sign-in · JavaScript SDK

​
How it works

Verify once. Carry the proof. Enforce before action.
  1. Verify once. Run a check through the hosted screen, MCP, or SDK.
  2. Carry the proof. NEUS saves the result with its current status and expiration when one applies.
  3. Enforce before action. Connected apps require that proof before access, payment, or execution.
Read the full flow in How verification works and Standards & interoperability.

​
Where NEUS sits

Login gets them in. Authority decides what they can do next. NEUS records the completed check as a portable proof another connected app can reuse.
  • Keep your sign-in, identity provider, payment, and agent framework.
  • Add NEUS via SDK, API, or MCP. No replacement required.
  • No wallet required. Work accounts, domains, social accounts, and passkeys all work. Wallet checks are optional.
See how teams put this to work in Solutions.

​
Status

NEUS is under active development. Published APIs and verifier schemas may change between minor versions before the long-term stability freeze. We version everything we ship and document every breaking change in the changelog.
Last modified on August 20, 2026