Where do assistants take action?
Assistants often work across developer tools, chat products, and production services. The same limits should apply in each place.
Agents are becoming portable. Their identity should be too.
Give each agent a persistent identity on your profile. Optional spend and action limits. Connected tools check that record instead of recreating it.
What AI teams can protect first
What does the industry buy first?
Start with clear action limits and spend caps for one assistant.
How do security partners join later?
The same proof model feeds review and revoke without forcing a second permission story for humans vs agents.
AI and automation in the NEUS productHow it works
Protect one sensitive assistant action
- 1Map the AI industry stackList frameworks, assistant tools servers, and developer tools agents that can already cause side effects.
- 2Pick the beachhead toolClear the first high-risk action path AI product owns end to end.
- 3Standardize on one proof modelReuse assistant ownership and permission proofs across developer tools and production.
- 4Invite security into the same objectShow revoke and review from the proof while keeping LangGraph and security monitoring.
Agent permission
Approved
Agentops-assistant
OwnerAcme Ops
Allowedread, draft, notify
Deniedtransfer, delete
Spend cap$25.00
Expires7 days
Connected tools confirm limits before a protected action runs.
Integration options
Use the path closest to your first protected decision.
- Hosted check
- Start without building a custom screen
- JavaScript
- Add the check to a product backend
- HTTP
- Check a proof from any service
- React
- Drop the flow into an existing interface
- Connect NEUS
- Bring checks into any chat, IDE, or job runtime
Bring the agent with you
Create or import an agent on your profile. Optional spend and action limits. Other systems check that record instead of starting over.
Explore on GitHubAgent permission
Approved
Agentops-assistant
OwnerAcme Ops
Allowedread, draft, notify
Deniedtransfer, delete
Spend cap$25.00
Expires7 days
Connected tools confirm limits before a protected action runs.
- Private by default
- Owners choose what each connected product can see.
- Checked when used
- Status, limits, and expiration are confirmed before the action.
- Reversible control
- Expired or revoked proofs stop approval immediately.
Useful next decisions
Agent and assistant permissionsCreate or import an agent. Optional spend and action limits.Portable proofsReuse completed checks across connected productsKeep the agent across toolsCreate or import an agent on your profile. Optional spend and action limits. Other systems check that record instead of starting over.
AI platform questions
Plain answers for teams using assistants to post, pay, or change data.