Skip to main content
Your AI has access. NEUS gives it authority. Private proofs of identity, provenance, and authority. Checked before action. Reused everywhere.

Identity

Humans, organizations, and agents. Portable across every connected app.

Provenance

Who owns it. Where it came from. Travels with the actor.

Authority

Spend caps, revocation. Checked before tools run.

​
Connect in one command

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

​
Authority before tools

Control an agent

Identity, spend caps, revocation. Enforced before action.

Gate and monetize

One link owns checks, price, and sign-in.

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.
See the full flow: How verification works · Proof lifecycle · Proof links and versioning.

​
Where NEUS sits

Login gets people in. Authority decides what they can do next. NEUS records that authority as a portable proof any connected app can check.
  • Keep your sign-in, identity provider, payment, and agent framework.
  • Add NEUS via SDK, API, or MCP. No replacement required.
  • Wallet checks are optional. Work accounts, domains, social accounts, and passkeys all work.
See how teams put this to work: Solutions.
Last modified on August 13, 2026