Who is acting?
Connect an agent identity to its controller so each system can distinguish an approved assistant from an unknown caller.
AI and automation
Control what agents can do—before they act.
Bind each agent or assistant to a checkable identity and controller-approved limits. Connected systems can confirm allowed actions, denied actions, spending caps, expiration, and revocation before supported work runs.
01Decisions that matter
One proof path across the highest-value gates.
Agent and assistant identity, delegated authority, tool access checked before action, spending controls, and reviewable trust decisions.
AI and automation gates
Ready
- Agent identityBound
- Allowed actionsScoped
- Spend capEnforced
What may it do?
Carry allowed and denied actions, spending limits, and expiration in one reusable permission proof.
Is approval still current?
Check status and revocation again at the protected tool call instead of trusting a stale setup decision.
02How it works
From trust decision to reusable proof in four steps.
- 01
Register the agent
Create a stable identity for the assistant or automation.
- 02
Set its limits
Choose approved actions, denied actions, spending, and expiration.
- 03
Connect the action path
Add the NEUS check to the supported tool or workflow.
- 04
Check before action
Require a current permission proof before protected work runs.
How it works
CHECK → RECEIPT
- 01Verify onceComplete a supported check
- 02Get a receiptResult becomes a reusable record
- 03Check at the gateApps confirm before action
- 04Share lessPresent the result, not the file
03Recommended paths
Start with the decision you already repeat.
Add one current proof to one valuable gate. Expand only when another product can reuse the same decision.
Trust receipt
Current
One check. Reusable everywhere it is accepted.
SubjectAcme Ops · org
CheckOrganization
ScopeAccess · payout
StatusActive
Expires2026-12-01
Connected apps confirm status before access — without the full source file.
Recommended NEUS paths
Pick the product that matches your gate.
Add one trusted decision to your next gate.
Start with a supported check, issue the reusable proof, and require current status where it matters.