NEUS Docs

Register the agent on your profile, then grant what it may do. Gates, APIs, and connected assistant tools can check those receipts before an action. The same account can complete both steps, or one account can register the agent while another approves its permissions.

Roles

Role	Does	Signs with
Agent	Registers identity (name, type, capabilities)	Agent wallet
Approver	Grants permissions and limits	Controller account

Together, the identity and permission receipts tell an integration who the agent is and what it may do.

Agent wallet — identifies the agent in NEUS and self-signs agent-identity.
Controller account: the approving account that signs agent-delegation. It does not need to own the agent wallet.

Permission limits

A permission receipt defines what the agent may do:

Concept	Field	Notes
Allowed actions	`allowedActions`	Empty means permissive (unless denied)
Denied actions	`deniedActions`	Always wins over allowed
Scope	`scope`	Defaults to `global`; use `payments:x402` for metered pay
Spend cap	`maxSpend`	Whole-number string in token base units (USDC: 6 decimals)
Expiry	`expiresAt`	Unix milliseconds; set when money or risk is in scope

Capabilities such as wallet, signing, spending, and publishing describe what an agent can do. The permission receipt decides what it is allowed to do.

Setup state

Field	Meaning
`linked`	Identity and permission receipts are both present
`principal`	Signed-in account from the current NEUS session

Overview

Start here.

Permissions

Full field reference.

Flow

Setup order.

Cookbook

Recipes.

Agent Trust

Agent concepts

Roles

Permission limits

Setup state

Next

Overview

Permissions

Flow

Cookbook

​Roles

​Permission limits

​Setup state

​Next

Overview

Permissions

Flow

Cookbook

Roles

Permission limits

Setup state

Next