AIP
AI Interaction Protocol
Agent-Web Communication Standard

AIP for Agent Developers

Build agents that read websites faster, cheaper and with less noise.

Instead of forcing your agents to crawl and interpret raw HTML, AIP allows them to check a structured manifest first and interact with websites through a cleaner protocol layer.

Why support AIP in your agents

When agents browse the web today, they usually waste resources parsing pages that were designed for humans, not machines.

AIP gives your agents a direct structured entry point into the website.

This reduces:

• crawling • token usage • latency • infrastructure cost • parsing noise

For multi-agent systems or large-scale workflows, these savings become significant.

Recommended discovery flow

The recommended AIP-compatible behavior for agents is: 

1. Visit the target domain
2. Check for /.well-known/aip.json
3. If found, load the manifest
4. Read priority_paths, ignore_paths and endpoints
5. Use AIP endpoints before attempting full HTML crawling
6. Fall back to HTML crawling only if AIP is unavailable

This approach lets your agent work more efficiently while preserving compatibility with the existing web.

Minimal discovery example (Python)

import requests

def fetch_site(url):
    aip_url = url.rstrip("/") + "/.well-known/aip.json"

    try:
        response = requests.get(aip_url, timeout=5)
        if response.status_code == 200:
            manifest = response.json()
            return {
                "mode": "aip",
                "manifest": manifest
            }
    except Exception:
        pass

    return {
        "mode": "html",
        "message": "Fallback to traditional crawling"
    }

Minimal discovery example (JavaScript)

async function fetchSite(url) {
  const aipUrl = url.replace(/\/$/, "") + "/.well-known/aip.json";

  try {
    const response = await fetch(aipUrl);
    if (response.ok) {
      const manifest = await response.json();
      return {
        mode: "aip",
        manifest
      };
    }
  } catch (error) {}

  return {
    mode: "html",
    message: "Fallback to traditional crawling"
  };
}

Why this matters for agent builders

AIP is not just another metadata format. It is a practical way to make agents more efficient when they interact with websites.

If your agent checks AIP first, it can:

• understand what the website is about • know which sections matter • skip useless routes • find retrieval and action endpoints • reduce expensive parsing work

This makes agents faster and cheaper to run.