For website owners
You already have email routing. agent.json just adds a front door that AI agents can find. Define actions, set parameters, get messages routed to the right inbox. No API to build, no integration to maintain.
Every major shift in the web created a new surface for interaction. HTML gave us pages. APIs gave us data. robots.txt gave us crawlability. Each was a small file that changed everything because it lowered the cost of the first interaction to zero.
agent.json is that file for the agentic web. A single discovery document at /.well-known/agent.json that turns any website from a destination humans visit into a service agents can talk to — and get answers from.
For website owners
You already have email routing. agent.json just adds a front door that AI agents can find. Define actions, set parameters, get messages routed to the right inbox. No API to build, no integration to maintain.
For agent builders
Stop scraping contact pages. Discover what any website accepts, call actions with validated parameters, and get structured responses back — all through one standard protocol.
For platforms
A standard that reduces agent-to-website interaction from a bespoke integration problem to a convention. Less friction means more transactions. More transactions mean more value for everyone.
For the ecosystem
The harder it is for agents to interact with websites, the more the agentic web concentrates around a few large platforms. An open protocol keeps the web decentralized by keeping the cost of participation low.
AI Agent Your Website | +-- GET /.well-known/agent.json --------> "What can I do here?" |<-- actions, schemas, auth, modes ------ | +-- POST /.agent/inbox -----------------> "Process this refund" |<-- { id, status: "routed" } ----------- | +-- GET /.agent/inbox/:id --------------> "Any response yet?" |<-- { response: { refund_id, amount } }-