The model
One account approves multiple agents. Each agent has a separate authority record with its ownallowedActions, deniedActions, and scope.
Why one wallet can support several agents
- No key sprawl. One wallet to manage, secure, and rotate.
- Per-agent authority. Give each agent only the actions, spending cap, and time window it needs.
- Traceable approvals. Each record identifies the agent, approving account, and permissions.
- Focused revocation. Revoke one agent’s authority without changing the others.
Set it up
1
Create each agent
Call
neus_agent_create for each team agent. Pass agentId, scope, delegationAllowedActions, delegationDeniedActions, skills, and instructions. The approving account signs the authority record.2
Confirm each agent
Call
neus_agent_link for each agent until linked: true.3
Connect each project
In each project where the agent should operate:Loads the agent’s identity, authority, skills, and context into the project.
4
Run under the right agent
Point each project or product workflow at the matching
agentId so actions run under that agent’s authority. Scheduled jobs live in the product UI when enabled for your account. They are not part of the thirteen public MCP tools.Skills
Each agent can list role-specific skills in its authority record. Skills describe capabilities.allowedActions and deniedActions determine what the agent may actually do.
Next
Agent authority
Full field reference for
allowedActions and deniedActions.Connect agent context
Load a verified agent’s identity and authority into a project.
Discover agents
Public pages, A2A, and EIP-8004 cards.
Agent setup
Step-by-step setup order.