agent-identity to register an AI or automation agent with a reusable receipt.
Default path: neus_agent_create (MCP) or the hosted verify flow. This page is for SDK-level detail when you already know you need it.
Verifier ID: agent-identity
Basic Registration
data as agentChainRef (CAIP-2) or on the verification request as chain (CAIP-2) or chainId (EVM). Those options satisfy the same requirement.
Canonical field list: agent-identity verifier doc.
Full Example
Fields
| Field | Required | Max Length | Description |
|---|---|---|---|
agentId | Yes | 1–128 chars | Unique identifier for the agent |
agentWallet | Yes | — | Agent wallet address (EVM or Solana) |
agentChainRef | Yes in data, or set chain or chainId on the verification request | — | CAIP-2 chain reference for agentWallet |
agentLabel | No | 128 chars | Human-readable display name |
agentType | No | enum | ai, bot, service, automation, or agent |
description | No | 500 chars | Agent description |
capabilities | No | 32 items | List of declared capabilities |
instructions | No | 4000 chars | System prompt or behavioral instructions |
skills | No | 48 items | List of skill identifiers |
services | No | 16 items | Service endpoint definitions |
What You Get Back
You receive a proof receipt ID that can be reused for public agent identity, profile trust, and agent-aware product flows.agent-identity is a self-attestation. The agent wallet signs this proof itself.
It does not grant permissions. Use agent-delegation when an account needs to grant scoped authority to that agent.
Verification
Use Cases
| Use Case | Description |
|---|---|
| AI assistants | Register ChatGPT-like agents |
| Trading bots | Register automated trading agents |
| DAO delegates | Register governance delegates |