Three discovery paths
| Path | URL | Returns |
|---|---|---|
| NEUS agent page | https://neus.network/agent/{agentId} | Human-readable agent profile |
| NEUS universal API | https://neus.network/api/agent/{agentId}?format=json | Identity + delegation + proofs |
| A2A / EIP-8004 | https://neus.network/api/agent/{agentId}?format=a2a | Agent card per A2A spec |
Example
If you registered an agent withagentId: "my-support-agent", you can discover it three ways:
Agent page:
What a card shows
| Field | Source | Visible |
|---|---|---|
agentId | agent-identity proof | Public |
agentWallet | agent-identity proof | Public |
agentLabel | agent-identity proof | Public |
description | agent-identity proof | Public |
capabilities | agent-identity proof | Public |
skills | agent-identity proof | Public |
controllerWallet | agent-delegation proof | Public |
scope | agent-delegation proof | Public |
allowedActions | agent-delegation proof | Owner-view only |
deniedActions | agent-delegation proof | Owner-view only |
allowedActions, deniedActions, approvalPolicy) are owner-view only — they are not exposed in public card responses. External consumers see the agent’s identity, capabilities, and controller, but not the internal permission boundaries.
How integrators use it
- Discover — fetch the agent card to learn what the agent is and who controls it.
- Verify — check the delegation proof to confirm the controller trusts the agent wallet.
- Delegate — if building on NEUS, create your own delegation to the agent for your app’s scope.
- Act — call the agent through MCP, A2A, or your runtime with confidence in its identity.
Next
Team agents
One controller, many scoped agents.
A2A
Full A2A and EIP-8004 spec.
Agent identity
Register an agent.
Overview
Start here.