Open Standard — Draft v1.0

Declare any web surface
agent-ready.

Agent Web Protocol defines agent.json — a machine-readable file that tells AI agents what a website can do, how to authenticate, and what actions are available. What robots.txt did for crawlers, agent.json does for agents.

Read the SpecView on GitHubagent.json Reference
/.well-known/agent.json
{
  "protocol": "awp/1.0",
  "agent_ready": true,
  "capabilities": {
    "actions": ["search", "book", "purchase"],
    "auth": "oauth2"
  }
}
The Pattern

A familiar evolution

Every era of the web introduced a simple, declarative file that unlocked a new layer of machine interaction. AWP continues this pattern for the age of AI agents.

1994
robots.txt
Told crawlers where they could go
2011
schema.org
Told search engines what things meant
2026
agent.json
Tells AI agents what they can do
Why AWP

What the protocol defines

Discovery

Well-known endpoint

Agents discover capabilities via /.well-known/agent.json — no scraping, no guessing, no prompt injection.

Capabilities

Structured actions

Declare what actions are available — search, book, purchase, submit — with typed parameters and descriptions.

Auth

Secure by default

Supports OAuth 2.0, API keys, and session-based auth with explicit scope declarations.

Schema

Machine-readable

JSON schema-based format that's easy for agents to parse and for humans to write and review.

Middleware

Synthetic generation

Middleware tools can generate a synthetic agent.json for any URL on demand, bridging the gap for sites that haven't implemented the standard yet.

Open

Community-driven

MIT-licensed, open-source specification. Built in public, governed by the community.

The agentic web starts with a file.

Add agent.json to your site and let AI agents understand what you offer.

Read the SpecificationContribute on GitHub