Skip to main content
Don’t restart from zero. Every new app makes you reconnect yourself. Re-prove ownership. Reconfigure permissions. Reattach tools. NEUS collapses that cost. One private profile for your identity, context, permissions, and proof. Portable across apps, agents, services, and transactions. Built for people and AI.

Profile

What should persist. Identity, context, permissions, and proof in one private place.

Proof

What travels. A reusable artifact any connected system can check.

Gate

What is allowed. Enforce authority before access, action, or payment.

​
Your AI shouldn’t start from zero either

Give any agent the identity, context, tools, permissions, and proofs it needs without rebuilding everything for every model or framework. Same profile. New agent. Your AI has access. NEUS gives it authority.

​
Connect in one command

Confirm the connection is live:
One setup. Same identity, provenance, and limits in Cursor, Claude Code, Codex, and production.

​
Or paste this into your agent

Copy the block below into Claude Code, Cursor, Codex, or any coding agent with NEUS MCP. The agent reads it, runs setup, signs you in, and starts carrying your authority.

​
What you can build

Control an agent

Identity, spend caps, revocation. Enforced before action.

Gate and monetize

Gate once. Monetize every qualified visitor.

Ship with the SDK

Hosted check, server confirm, React gate.

Wire MCP tools

One endpoint. Any agent, editor, or server.

Check before action

Run once, save the proof, reuse everywhere.

Read the API

Hosted checks, proofs, authority, billing. OpenAPI.

​
How it works

Verify once. Carry the proof. Enforce before action. Frameworks run tools. Models think. NEUS checks identity, provenance, and authority before sensitive actions.
  1. Verify once. Run a check through the hosted screen, MCP, or SDK.
  2. Carry the proof. NEUS saves the result with its status, allowed use, and expiration.
  3. Enforce before action. Connected apps require that proof before access, payment, or execution.
Read the full flow in How verification works, Proof lifecycle, and Proof links and versioning.

​
Where NEUS sits

Login gets them in. Authority decides what they do next. NEUS records that authority as a portable proof any connected app can check, so trust travels with the actor, not the app.
  • 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 18, 2026