agent-identity
Proof skills are metadata only — they do not install MCP servers.
Setup
Check
Call
neus_context, then neus_agent_link with the agent address. If linked: true, you are done.Create
Call
neus_agent_create with agentId and agentWallet. Finish on NEUS via hostedVerifyUrl or the returned signing steps.agentWallet to "generate" when NEUS should create a new agent key. Save returned key material in your secrets manager.
Agent create · Agent verification flow
SDK
For server-side or custom signing:Fields
| Field | Required | Description |
|---|---|---|
agentId | Yes | Unique id (1–128 chars) |
agentWallet | Yes | Agent address (EVM or Solana) |
agentLabel | No | Display name |
agentType | No | ai, bot, service, automation, or agent |
description | No | Short description (500 chars) |
capabilities | No | Feature flags — see schema |
instructions | No | System prompt and policy (16000 chars) |
skills | No | Up to 48 skill objects (id required) |
services | No | Up to 16 endpoints (name + endpoint) |
agent-identity.json.
Result
You get a receiptqHash, signed by the agent address. This registers identity only. Add agent-delegation for permissions.
Check status
neus_agent_link or neus_proofs_check.