Create or import
Link the agent to the person or organization that owns it. Default is the signed-in profile.
Your agents should not reset at every boundary.
Create or import an agent linked to your profile. Add a separate spend account only when you need one. Connected runtimes check identity, permissions, and history instead of asking who the agent is again.
A record other systems can check
Optional limits
Spend, allowed actions, expiry, and revoke. Add a separate spend account only when you need one.
Other systems check
The next tool, marketplace, or runtime confirms the record is still current instead of starting over.
Keep the agent across tools in the NEUS productHow it works
Create or import, optional limits, then carry
- 1Connect NEUSAdd the hosted endpoint once, then sign in.
- 2Create or import the agentLink it to your profile. Generate a dedicated spend account only when you need one.
- 3Set optional limitsAllowed actions, spend cap, expiry, and revoke.
- 4List or move the agentOther marketplaces can list the same agent. The identity stays portable.
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
What stays true
Clear checks at the moment they matter.
- Create or import on the signed-in profile
- Optional separate spend account
- Other systems check instead of starting over
Questions about portable agents
How identity, limits, and listings work when the agent changes tools.