Protocol

Schema Reference

All 6 AWP schemas — every field, every constraint, every example.

Recommended Folder Structure

AWP relies on predictable paths. This is the standard directory layout for an AWP-compliant website:

Project Structure
/ (Root of your website)
├── .well-known/
│   └── agentic-web-protocol.json  # 1. Discovery Manifest (Entry point)
└── awp/
    ├── manifest.json              # 2. Full Site Manifest
    ├── content/
    │   ├── structure.json         # 3. Content Navigation Tree
    │   └── feeds/
    │       └── updates.json       # 4. Incremental Updates Log
    ├── api/
    │   └── tools/
    │       └── functions.json     # 5. Callable AI Functions
    └── mcp/
        └── mcp.json               # 6. Model Context Protocol config

Core Manifests

These two files form the absolute foundation of your agentic integration.

1. Discovery Manifest

Published at /.well-known/agentic-web-protocol.json. The first file any AWP-aware agent fetches.

Field	Type	Required	Description
`version`	string	required	Semver string e.g. "1.0"
`name`	string	required	Human-readable site name. Max 200 chars.
`description`	string	required	Brief description. 10–500 chars.
`capabilities`	string[]	required	content \| api \| search \| mcp \| analytics
`endpoints`	object	required	Path map. manifest field is required inside.
`authentication`	object	optional	Auth requirements for agents.
`rate_limits`	object	optional	Per-minute and per-day request limits.
`agent_instructions`	uri-ref	optional	Path to etiquette file for agents.
`updated_at`	datetime	optional	ISO 8601 timestamp of last update.

discovery.example.json
{
  "version": "1.0",
  "name": "ML Research Hub",
  "description": "Comprehensive ML research, tutorials, and datasets for AI agents.",
  "capabilities": ["content", "search", "api", "mcp"],
  "endpoints": {
    "manifest": "/awp/manifest.json",
    "content": "/awp/content/",
    "api": "/awp/api/",
    "mcp": "/awp/mcp/mcp.json"
  },
  "authentication": {
    "required": true,
    "methods": ["api_key"],
    "registration": "/awp/auth/register"
  },
  "rate_limits": {
    "requests_per_minute": 60,
    "requests_per_day": 10000,
    "tokens_per_request": 4096
  },
  "agent_instructions": "/awp/instructions.md",
  "updated_at": "2025-01-15T10:30:00Z"
}

2. Full Manifest

Lives at /awp/manifest.json. Contains full site metadata, capability config, CORS, and caching hints.

Field	Type	Required
`awp_version`	string	required
`site`	object	required
`content`	object	required
`capabilities`	object[]	required
`api`	object	optional
`cache_control`	object	optional
`cors`	object	optional
`agent_hints`	object	optional

Schemas designed to help AI agents read and traverse your website's documentation and pages.

3. Content Structure

Lives at /awp/content/structure.json. Maps your entire content tree.

structure.example.json
{
  "version": "1.0",
  "site_name": "ML Research Hub",
  "generated_at": "2025-01-15T10:30:00Z",
  "total_pages": 142,
  "total_tokens": 850000,
  "sections": [
    {
      "id": "tutorials",
      "title": "Tutorials",
      "token_count": 120000,
      "pages": [
        {
          "title": "Getting Started with PyTorch",
          "path": "/tutorials/pytorch-intro",
          "token_count": 3200,
          "tags": ["pytorch", "beginner"]
        }
      ]
    }
  ]
}

4. Updates Schema

Lives at /awp/content/feeds/updates.json. Incremental change log so agents can sync without re-fetching everything.

updates.example.json
{
  "version": "1.0",
  "last_sync": "2025-01-15T10:30:00Z",
  "sync_interval_seconds": 86400,
  "changes": [
    {
      "type": "created",
      "id": "page-transformer-guide",
      "timestamp": "2025-01-15T09:00:00Z",
      "path": "/tutorials/transformers",
      "title": "Transformer Architecture Deep Dive",
      "token_count": 5200
    }
  ],
  "has_more": false
}

Tools & Execution

Schemas that expose interactive capabilities, APIs, and secure tool execution pointers to LLMs.

5. Functions Schema

Lives at /awp/api/tools/functions.json. Declares callable API functions — agents can invoke these directly.

functions.example.json
{
  "version": "1.0",
  "functions": [
    {
      "name": "search_content",
      "description": "Full-text search across all site content. Returns ranked results.",
      "parameters": {
        "type": "object",
        "properties": {
          "query":  { "type": "string",  "description": "Natural language query" },
          "limit":  { "type": "integer", "description": "Max results (1-50)", "default": 10 }
        },
        "required": ["query"]
      },
      "tags": ["search", "content"]
    }
  ]
}

6. MCP Schema

Lives at /awp/mcp/mcp.json. Minimal pointer: where the MCP server is and how to authenticate.

Field	Type	Required	Description
`url`	uri	required	Full URL to the MCP server endpoint
`transport`	enum	required	http (recommended) \| sse (legacy) \| stdio
`authentication`	object	optional	Auth type and credential delivery config
`mcp_version`	string	optional	MCP protocol version e.g. "2024-11-05"