Skip to main content
Use this flow when you need to identify an agent, define what it can do, and let an app or AI runtime consume that result. For definitions of approving account, agent wallet, and session, see Agent concepts.

​
What this flow includes

  1. Agent registration
  2. Optional agent permissions
  3. A runtime such as MCP or the API that consumes the result
1

Register the agent

Create an agent registration proof that binds the agent wallet and its public metadata to one reusable proof receipt.
2

Add agent permissions when an approving account is involved

If a person, team, or service is granting authority to the agent, create an agent permissions proof with scope, permissions, and any limits.
3

Use MCP or the API in the runtime

Your app, agent runtime, or tool can read the verifier catalog, check access, and send users to hosted verify when interactive completion is still needed.
agent-identity registers the agent. agent-delegation grants authority. Keep those two concepts separate in your app and docs.

​
What you configure

  • The agent wallet
  • The agent label, type, and public description
  • Optional permissions, scope, expiry, and limits when an approving account is granting authority

​
What your app gets back

  • A proof receipt ID for agent registration
  • An optional proof receipt ID for agent permissions
  • A stable way to reuse those results in hosted verify, MCP, and API checks

​
Hosted handoff

When neus_agent_link (MCP) returns status: "link_required", the default path is simple:
  1. Open the hostedVerifyUrl from the tool response.
  2. Finish the guided browser flow.
  3. Call neus_agent_link again to confirm identity and access approval are both on file.
You do not need to build or manage the hosted URL yourself for the normal MCP path. This tool is a readiness check (identity + permissions), not a wallet-linking flow.

Concepts

Approving account, agent wallet, and API field names.

Agent Registration

Register a verifiable agent.

Agent Permissions

Define delegated authority and limits.

MCP Server

Connect proofs to agent tools and runtimes.