skills are metadata only - they do not install MCP servers - MCP overview. Prefer portable skill ids (spec, directory).
Default: neus_agent_create (MCP) or hosted verify. Below = SDK detail.
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.
Field names and limits: Fields (below). JSON Schema: agent-identity.json.
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 | - | Boolean flags (search, mcp, proofs, …) - see schema |
instructions | No | 16000 chars | System prompt, tool/connector policy, output format, and safety/PII handling; portable in the signed identity |
skills | No | 48 objects | Each object requires id; optional kind, label, … |
services | No | 16 items | name + endpoint (+ optional version) |
What you get
Verification id. Signed with the agent wallet. No spend or permission grants - useagent-delegation for scoped authority.