Skip to main content
NEUS gives AI agents and assistants a portable identity plus explicit permissions. Connected runtimes check those receipts before granting access or allowing a sensitive action. Agent frameworks handle reasoning and execution. NEUS supplies verifiable identity, permission limits, and reusable trust receipts.

​
Two receipts make an agent ready in NEUS

  • Identity (agent-identity): the agent account signs its name, type, capabilities, and skills. Identity alone grants no permission.
  • Permissions (agent-delegation): an approving account signs the allowed actions, spending cap, and expiration date.
An agent is ready only when both are on file.

​
Permission limits

The permission receipt defines a boundary:
  • allowedActions / deniedActions: explicit allow and deny lists. A denied action takes precedence.
  • maxSpend: a whole-number spending cap in token base units. USDC uses six decimals, so 25 USDC is "25000000".
  • scope: the area where permissions apply, such as payments:x402 or global.
  • expiresAt: expiration time in Unix milliseconds. Set it for payments or other sensitive actions.
Quick setup presets (full-access, payments, readonly, automation) are available through neus_agent_create. Full field reference: Agent delegation.

​
Set it up

1

Connect

Configures hosted NEUS MCP for Cursor, Codex, VS Code, or Claude Code.
2

Check

Call neus_context, then neus_agent_link with the agent wallet.
3

Create

If identity or permission receipts are missing, call neus_agent_create. The agent account signs its identity, and the approving account grants permissions.
4

Confirm

Call neus_agent_link until linked: true, then reuse receipts.
5

Connect

In your project repo:
Loads the agent’s verified identity, permissions, and rules into the project. Connect agent context.
6

Act

Check receipt status before payments, data access, or other sensitive actions.

​
Next

Verification flow

Step-by-step order.

Agent identity

Register an agent.

Agent permissions

Grant allowed actions, spending caps, and expiration dates.

Discover agents

Public pages, A2A, and EIP-8004 cards.

Pay per call

Charge for API requests with HTTP 402.

Connect agent context

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

MCP setup

Connect supported editors with OAuth or an access key.
Last modified on July 14, 2026