Discovery paths
Per-agent cards resolve to
GET https://api.proofable.me/api/v1/agents/card/{agentId}. The platform A2A card is also available at /api/agent/config?format=a2a. Proofable is agent 1135859 in the ERC-8004 Identity Registry on Base (eip155:8453:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432). Its registration file is https://proofable.me/.well-known/agent-registration.json, and the platform metadata reports the same entry under erc8004. The pinned bytes of that file, with the registry read that binds the URI to the signing account, are in public/evidence/registry. Each public agent has its own registration file at the per-agent ERC-8004 URL above; a private agent’s URL returns 403.
Examples
What a card shows
Public callers see who the agent is and who approved it. The full allow and deny lists are visible to the owner only.
Visibility
An agent is its identity proof, so it has one visibility setting with the same three values every Proofable proof has. The setting covers the whole agent, including its instructions.
An Unlisted card is link-addressed, like a proof. A
GET on its URL returns it to any caller, and it never appears in a listing. Hand it to someone directly.
A Private agent:
- answers
403witherror.code = "AGENT_NOT_PUBLIC"to a caller with no access, so you can tell “exists but not shared with you” apart from404 AGENT_NOT_FOUND; - opens fully for the owner and for anyone holding a live access grant on that agent’s identity proof.
POST /api/v1/verification/access/grant), stored against the identity proof’s qHash. A granted viewer sees the agent exactly as the owner does. An expired or revoked grant falls back to 403.
The owner changes visibility from the agent’s Share sheet, which edits the identity proof in place. The change takes effect on the same link immediately.
CORS and caching
Discovery endpoints returnAccess-Control-Allow-Origin: *. Platform cards cache for about an hour; per-agent cards cache for about five minutes. A card served to its owner is never cached publicly.
Platform A2A card
The platform card includes registered skills, MCP, REST and payment interfaces, auth options (OAuth and access keys), and networks listed by CAIP-2 id.Agent identity
Register an agent so it appears in discovery.
Connect agent context
Mount a verified agent into a project.