Skip to main content
A NEUS profile can manage multiple agents under one approving account. Each agent gets its own identity and permission receipt. Agents may share an operating wallet while keeping different limits.

​
The model

One account approves multiple agents. Each agent has a separate permission receipt with its own allowedActions, deniedActions, and scope.
The permission receipt, not the shared key, separates the agents. Each integration checks the receipt before allowing an action.

​
Why one wallet can support several agents

  • No key sprawl. One wallet to manage, secure, and rotate.
  • Per-agent limits. Give each agent only the actions, spending cap, and time window it needs.
  • Traceable approvals. Each permission receipt identifies the agent, approving account, and limits.
  • Focused revocation. Revoke one agent’s permissions 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 permission receipt.
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, permissions, 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 permission receipt. 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 permission receipt. Skills describe capabilities; allowedActions and deniedActions determine what the agent may actually do.

​
Next

Agent permissions

Full field reference for allowedActions and deniedActions.

Connect agent context

Load a verified agent’s identity and permissions into a project.

Discover agents

Public pages, A2A, and EIP-8004 cards.

Verification flow

Step-by-step setup order.
Last modified on July 14, 2026