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 receipt 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 receipt.
For developers
Set up once. Use the same rules everywhere.
Connect NEUS to your assistant, then use the same checks before tools take sensitive actions.
Add to
~/neus
LiveOne receipt across every integration option
Keep one result everywhere
Every path reads the same receipt status, limits, and expiration.
Add another path later
Add a second integration after the first protected decision works with a current receipt.
NEUS | reusable receipt
Portable
One proof. Every surface that accepts it.
- First useVerify once
- Next appReuse
- Agent actionReuse
- Network effectCompounds
Profile owners control visibility. Connected systems check status.
How it works
Choose, check, protect, expand
- 1Choose an integration pathChoose a ready-made screen, JavaScript, React component, or assistant setup.
- 2Create the first receiptComplete one supported check end to end.
- 3Protect one decisionRequire current status before access, payment, or an assistant action.
- 4Add the next surfaceReuse the same receipt model so every integration reads the same status and limits.
How it works
CHECK | RECEIPT
- 01Verify onceComplete a supported check
- 02Get a receiptResult becomes a reusable record
- 03Check before accessApps confirm before action
- 04Share lessPresent the result, not the file
What stays true
Clear checks at the moment they matter.
- The same receipt 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.