{
 "acronym": "",
 "adoption": {
  "by": null,
  "level": "unmeasured",
  "probe_run": null
 },
 "aliases": [],
 "analog": "robots.txt, but for in-page actions rather than URL fetches",
 "collisions": [],
 "discovery": {
  "mechanism": "well-known file, overridable per-page by an HTML <link rel=\"agent-permissions\"> element",
  "path": "/.well-known/agent-permissions.json"
 },
 "dispute": null,
 "evidence": [
  {
   "claim": "The las-wg/agent-permissions.json GitHub repository publishes a complete JSON Schema (metadata, strict default, resource_rules with an enumerated verb list including read_content/click_element/submit_form/execute_script/upload_file, action_guidelines with RFC 2119 directives, and an api block referencing OpenAPI/MCP/A2A endpoints), discoverable at /.well-known/agent-permissions.json or via a <link rel=\"agent-permissions\"> tag.",
   "date": "2026-07-17",
   "label": "VERIFIED",
   "url": "https://github.com/las-wg/agent-permissions.json"
  },
  {
   "claim": "An arXiv paper by the Lightweight Agent Standards Working Group, 'Permission Manifests for Web Agents,' independently describes the same manifest structure, discovery paths, and positions it against MCP/A2A and OpenAPI as complementary rather than competing.",
   "date": "2026-01",
   "label": "VERIFIED",
   "url": "https://arxiv.org/html/2601.02371v2"
  }
 ],
 "form": "well-known-file",
 "governance": "Lightweight Agent Standards Working Group (LAS-WG), an open community project hosted on GitHub at las-wg/agent-permissions.json; no formal standards-body affiliation found",
 "group": null,
 "history": [
  {
   "date": "2026-09-06",
   "note": "created and verified against github.com/las-wg/agent-permissions.json and arxiv.org/html/2601.02371v2 (occupant-diff candidate)"
  }
 ],
 "id": "agent-permissions-json",
 "implementation": "unknown",
 "last_verified": "2026-09-06",
 "name": "agent-permissions.json",
 "native_status": "v1.0.0, complete JSON Schema published; described by the working group's own arXiv paper as a proposal, not an adopted standard",
 "origin": {
  "date": "2026-07",
  "org": "Lightweight Agent Standards Working Group (LAS-WG)"
 },
 "part_of": null,
 "parties": [
  "agent-site"
 ],
 "phase": "candidate",
 "probe": {
  "method": "GET",
  "on_absent": "No agent-permissions.json at the well-known path; also check the page's HTML for a <link rel=\"agent-permissions\"> override before concluding the site has not published page-action permissions",
  "parse": "Valid JSON with top-level 'metadata' (schema_version, last_updated) and 'strict' boolean fields present, per the LAS-WG JSON Schema",
  "path": "{origin}/.well-known/agent-permissions.json"
 },
 "question": "Which page-level interactions (clicking, form submission, file upload, media control, script execution) may an agent perform while driving a web page's UI, as opposed to just fetching it?",
 "scope": "general",
 "spec_url": "https://github.com/las-wg/agent-permissions.json",
 "step": "permit",
 "summary_md": "agent-permissions.json is a JSON manifest format, published at v1.0.0 by the Lightweight Agent Standards Working Group (LAS-WG), that lets a website declare which in-page interactions an AI agent driving its UI may or may not perform [1]. It targets a permit-layer gap that robots.txt and AIPREF/Content-Signals leave open: those govern whether a URL may be fetched and what a fetched page's content may be used for, but say nothing about what an agent already on the page is allowed to click, type into, submit, upload, or execute once it is rendering and interacting with the DOM directly, as browser-using agents increasingly do [2].\n\nThe schema, fully published in the repository, defines a top-level `strict` boolean setting the default posture (forbid-by-default vs. allow-by-default), an array of `resource_rules` scoping specific verbs (from a fixed enum including read_content, click_element, submit_form, execute_script, upload_file, and others) to CSS selectors with optional rate-limit/time-window/human-in-the-loop modifiers, a set of `action_guidelines` expressed as RFC 2119 MUST/SHOULD directives for behaviours too fuzzy to capture as selector rules, and an `api` block that points an agent toward an OpenAPI, MCP, or A2A endpoint as a preferred alternative to driving the UI at all [1][2]. It is discoverable at the fixed path `/.well-known/agent-permissions.json` or overridden per-page via an HTML `<link rel=\"agent-permissions\">` tag.\n\nIt does not govern whether a URL may be crawled in the first place (robots.txt's job), does not define content-use-after-fetch permissions (AIPREF/Content Signals' job), and does not define authentication or payment. Governance is informal: LAS-WG presents itself as an open working group with a GitHub org and a companion arXiv paper, not a submission to IETF, W3C, or any chartered standards body, and no version history beyond 1.0.0 (published 2026-07-17) was found in this pass.\n\nAs of this verification (2026-09-06), the spec text and JSON Schema are complete and internally consistent across both the GitHub repository and the independently-hosted arXiv paper, which is enough for two independent primary sources; however, this pass found no production website actually serving a live agent-permissions.json file, and no browser-agent product (e.g. a computer-use or browsing agent framework) documented as consuming it, so implementation is recorded as unknown rather than shipping or none-found. What is unresolved: whether LAS-WG has any institutional backing beyond its own GitHub organization; whether any of the browser-driving agent vendors (OpenAI Operator-style agents, Anthropic computer use, browser extensions) have committed to reading this file; and how it will interact with the pre-existing, differently-scoped `agents.json` API-discovery convention it explicitly distinguishes itself from in its own comparison table.",
 "track": "community",
 "version": {
  "date": "2026-07-17",
  "label": "1.0.0"
 },
 "url": "https://agenticweb.wiki/protocols/agent-permissions-json/",
 "category": "permit",
 "type": "protocol"
}