Choose the fastest starting point
Use a ready-made screen for speed, JavaScript for product code, React for a drop-in flow, or assistant setup for developer tools.
Use one proof across every way you build.
Start with a ready-made check screen, a few lines of code, a drop-in component, or assistant setup. Every option creates and reads the same proof.
For developers
Start with the shortest path.
Connect NEUS in any chat, IDE, or job runtime. Same profile, proofs, listings, and permissions.
Add to
~/neus
LiveOne proof across every integration option
Keep one result everywhere
Every path reads the same proof status, limits, and expiration.
Add another path later
Add a second integration after the first protected decision works with a current proof.
NEUS | reusable proof
Portable
One proof. Every surface that accepts it.
- First useRun check
- Next accepted appCheck proof
- Agent actionCheck scope
- Current statusRequired
Profile owners control visibility. Connected systems check status.
How it works
Choose, check, protect, expand
- 1Add a checkUse a ready-made screen, JavaScript, a React gate, or one assistant command.
- 2Create the first proofComplete one supported check end to end.
- 3Protect one decisionRequire current status before access, payment, or an assistant action.
- 4Add the next surfaceReuse the same proof model so every integration reads the same status and limits.
How it works
CHECK | PROOF
- 01Run a checkComplete a supported check
- 02Get a proofResult becomes a reusable record
- 03Check before accessIntegrated apps confirm before action
- 04Share lessPresent the result, not the file
What stays true
Clear checks at the moment they matter.
- The same proof works across ready-made screens and code
- A public JavaScript package for product teams
- Step-by-step guides for each integration path
Developer and install questions
Plain answers about ready-made screens, code, and assistant setup.