NEUS Docs | Verify once. Carry the proof.

Create the agent on your profile, then set what it may do. Gates, APIs, and connected assistants can read those results before an action. The same account can complete both steps, or one account can create the agent while another grants authority.

Roles

Role	Does	Signs with
Agent	Creates identity (name, type, capabilities)	Agent wallet
Approver	Grants authority and spend caps	Controller account

Together, identity and authority 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.

Authority

An authority record 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 authority record decides what it is allowed to do.

Setup state

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

Overview

Start here.

Permissions

Full field reference.

Flow

Setup order.

Cookbook

Recipes.

Agents

Agent concepts

Roles

Authority

Setup state

Next

Overview

Permissions

Flow

Cookbook

​Roles

​Authority

​Setup state

​Next

Overview

Permissions

Flow

Cookbook

Roles

Authority

Setup state

Next