An open standard for the agentic web

AI agents need operating instructions.

aiconfig.dev is a lightweight configuration standard that tells AI agents how to safely interact with your website, APIs, workflows, and humans.

/.well-known/aiconfig.json200 OK
{
  "version": "0.1",
  "allowed_actions": ["search_docs", "request_demo"],
  "human_approval_required_for": ["payment"]
}
01 — Context

Why this matters

The web already has conventions for crawlers, search engines, and language models. But AI agents are beginning to do more than read. They search, compare, book, submit, schedule, draft, and trigger workflows.

Acting safely requires more than content. It requires permissions, preferred endpoints, approval rules, identity, and auditability.

02 — The stack

The missing layer of the agentic web

robots.txt
tells crawlers where they can go
Crawlers
sitemap.xml
tells search engines what exists
Search engines
llms.txt
tells models what a site means
Language models
aiconfig.json
tells agents what they can do
Agents
03 — Mechanism

How it works

01

Publish a config

Add a simple config file at /.well-known/aiconfig.json or /aiconfig.json.

02

Agents discover it

Agents read the file before taking action on your site, APIs, or workflows.

03

Act within rules

Allowed actions, restricted actions, approval requirements, preferred endpoints, auth expectations, and audit behavior — all declared.

04 — Specification

Example config

A minimal aiconfig.json declaring entrypoints, allowed and restricted actions, approval requirements, agent auth, and audit behavior.

/.well-known/aiconfig.json
application/json
{
  "version": "0.1",
  "site": "https://example.com",
  "description": "Example business website",
  "agent_entrypoints": {
    "docs": "/llms.txt",
    "support": "/api/agent/support",
    "sales": "/api/agent/demo",
    "search": "/api/agent/search"
  },
  "allowed_actions": [
    "read_public_pages",
    "search_docs",
    "draft_support_ticket",
    "request_demo",
    "compare_products"
  ],
  "restricted_actions": [
    "complete_purchase",
    "change_account_settings",
    "delete_data",
    "sign_contract"
  ],
  "human_approval_required_for": [
    "payment",
    "legal_commitment",
    "account_change",
    "personal_data_export"
  ],
  "auth": {
    "agent_auth_supported": true,
    "methods": ["oauth", "signed_agent_token"]
  },
  "audit": {
    "log_agent_actions": true,
    "provide_action_receipts": true
  }
}
05 — Adoption

Early use cases

Support

Route agents to the right support endpoint.

Commerce

Let agents compare products without completing purchases.

SaaS

Define onboarding, docs, and demo workflows.

Bookings

Allow search and draft reservations with human confirmation.

Operations

Expose safe workflow actions with approval rules.

DRAFT · v0.1

This is an early draft convention, not a formal standard. The goal is to start a practical conversation among builders, developers, founders, and agent platform teams.

Help define the agent-operable web.

If agents are going to act on behalf of users and businesses, websites need a simple way to publish their rules.