Skip to main content
Your AI has access. NEUS gives it authority. Prove who controls an agent, set exactly what it can do, and check those limits before it uses a sensitive tool, moves money, or accesses protected data. Keep your current model, agent framework, sign-in, and payment stack. NEUS adds the check before action.

Connect an assistant

One command, browser sign-in, then your first protected action.

Protect an app action

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

Sell gated 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.

​
Start here

One command. Then click Connect in your assistant.
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. Need the agent to do it? Connect NEUS.

​
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