Skip to main content
Every A-Identity surface serves a manifest at /.well-known/ai-agent-manifest.json. It is the agent-facing version of a sitemap. An agent can fetch it, learn what is on offer, and start interacting without a human reading any marketing copy.

What It Describes

Fetch It

Designed For Both Sides

The manifest is written for two readers at once. Agents read capabilities and endpoints to act. Humans read human_oversight to know what stays under their control. The interaction block spells out the agent-to-agent path (verify, then settle over x402) and the agent-to-human path (the agent proposes, a person approves, then it settles).
Keep the page source LLM-parsable. Plain structure, clear labels, and the manifest link in the page head let an agent navigate without guessing.