Skip to main content

​
Agent Verification Flow

NEUS agent integrations usually combine three layers:
  1. Agent identity proof
  2. Optional controller-to-agent delegation proof
  3. An execution surface such as MCP that can read trust signals or trigger hosted verification
1

Create an agent identity proof

Bind the agent wallet and agent metadata into a reusable proof receipt.
2

Create an agent delegation proof when a controller is authorizing the agent

Use delegation to define scope, permissions, and spend or disclosure constraints.
3

Use MCP or API surfaces to consume the resulting trust signals

Agents can inspect verifier catalog data, run gate checks, and hand users to hosted verify for interactive completion.

Agent Identity

Agent Delegation

MCP Server