Open Standard — Draft v0.1

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.

Get StartedRead the SpecView on GitHub
/.well-known/agent.json
{
  "awp_version": "0.1",
  "domain": "example.com",
  "intent": "Online store with search and checkout",
  "actions": [
    { "id": "search", "method": "GET", "endpoint": "/api/search" },
    { "id": "purchase", "method": "POST", "endpoint": "/api/purchase" }
  ]
}
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.

Tooling

CLI and editor support

Generate with npx agent-json init, validate files, or add native support to Claude Code via the AWP MCP server.

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.

Generate yours nowRead the Specification