Browser extension

The AOM Surface Explorer is a Chrome/Chromium extension that reads the current tab and shows AOM JSON in its popup—so you can preview or export what an agent would see. It does not change your site or inject scripts into the page; publishing AOM still means deploying policy and JSON-LD yourself (see Getting started).

Install from Chrome Web Store Manual ZIP download

What it does

  • Generate AOM — A content script reads the current page (DOM and any existing JSON-LD) and builds a best-effort AOM surface (aligned to spec/v0.1.0/aom-input-schema.json). The JSON is kept in the extension only (popup); nothing is written into the page.
  • Read / copy AOM — If the page already has <script type="application/ld+aom+json">, that native AOM is shown when valid. Otherwise the extension shows generated JSON in the popup. Copy or save for validate at aom.tools/validate or your own tooling.
  • Save AOM as file — Download the current surface as a *.aom.json file (name derived from surface id or path).
  • Basic validate — Quick structural check in the popup; for full validation use validate at aom.tools/validate or the schemas on agentobjectmodel.org.
  • Report issue / Feedback — Popup buttons open a mailto with the page URL and captured AOM snippet.

The extension does not modify page HTML. When you copy from the popup, you get pure JSON (no script wrapper); validators accept either raw JSON or a full script snippet.

Installing and using

  • Recommended: install from the Chrome Web Store listing, then pin the extension and open it on any http/https page.
  • Open chrome://extensions (or edge://extensions), enable Developer mode, then Load unpacked and select the extensions/chromium folder from this repo (or the unzipped folder from Downloads for surface owners).
  • On any http or https page, click the AOM Surface Explorer icon to open the popup. Use it to view, copy, or save the current page's AOM.

Browser compatibility

Manifest V3 extension; works on Chrome, Edge (Chromium), Brave, Vivaldi, Opera, and other Chromium-based browsers that support MV3. Ports to Firefox or Safari need separate manifests and API adjustments.