Skip to main content
Every registered NEUS agent has a public card — identity, controller, and capabilities other apps can check before they trust it.

Discovery paths

Per-agent EIP-8004 cards resolve to GET https://api.neus.network/api/v1/agents/card/{agentId}. The platform A2A card is also available at /api/agent/config?format=a2a.

Examples

What a card shows

Public cards do not expose full allow/deny lists. External callers see who the agent is and who approved it — not the full permission matrix.

Platform A2A card

The platform card includes registered skills, MCP / REST / payment interfaces, auth options (OAuth and profile access keys for servers), and supported networks (Base and Solana CAIP-2 ids).

Cross-chain identifiers

CORS and caching

Discovery endpoints return Access-Control-Allow-Origin: *. Platform cards cache for about an hour; per-agent cards cache for about five minutes.

How to use it

  1. Discover — fetch the card for the agent you need.
  2. Confirm — check the permission receipt before a sensitive action.
  3. Connect — call the agent through MCP, A2A, or your own runtime.

Next

Agent identity

Register an agent so it appears in discovery.

Team agents

One approving account, many agents.

Connect agent context

Mount a verified agent into a project.

MCP

Check receipts and resolve agents at runtime.
Last modified on July 14, 2026