Build with the record
Agent registration file
GET or HEAD /agent.json — retrieve the registration file hosted for an AI agent.
Request
Replace YOUR-AGENT with the actual registered name. This route is for agents using Entity.ID hosted registration files. Agents can use other storage URIs; read the URI recorded for the agent.
Host and network
- Host — the agent domain, such as YOUR-AGENT.ai.entity.id.
- network — optional mainnet or sepolia. Keep the query exactly as supplied by the registration URI.
- host — preview fallback on entity.id, for example ?host=YOUR-AGENT.ai.entity.id&network=sepolia. The value must be a valid agent domain.
Response and caching
HTTP 200 returns the stored registration file as JSON, without a data wrapper. The file is returned as stored. The response permits cross-origin reads and uses a 60-second public cache with stale-while-revalidate=300.
When the stored record has a CID, the response includes an ETag. Send it in If-None-Match to receive 304 when unchanged. HEAD returns the same status and headers without a body.
Errors
- 400 — unknown network.
- 404 — not found, or no registration file.
- 503 — registry unavailable. This response uses Cache-Control: no-store.
Trust and interpretation
Registration metadata describes an agent and its advertised services. It does not independently prove the quality, safety, or authority of every capability. Check the identity registry, owner, network, and evidence needed by your application.