Developer tools for agent-ready websites.

Install surfaces. Define policies. Validate JSON. Integrate agents.
Everything a developer needs to ship AOM — in one place.

I own a website → I build agents →

Or jump to: Downloads · Documentation · Validator · GitHub

GET STARTED

From zero to your first AOM surface in minutes.

Install Surface Explorer

Inspect any page's AOM surface JSON live in your browser.

Install from Chrome Web Store →

Define an AOM Surface

Add a small JSON file next to your page that describes tasks, entities, and your automation policy.

See surface examples →

Validate your JSON

Run the AOM validator to confirm your surface and policy are correctly formed before shipping.

Open the AOM Validator →

Integrate an Agent Kit

Use the official SDKs to build agents that read AOM surfaces. Available for Python 3, Node 18+, .NET 8, and Java 17.

Go to Downloads →

TOOLS

Everything you need to build with AOM.

Browser Extension

AOM Surface Explorer

Inspect and export any page's AOM surface JSON live. Works on Chrome, Edge, and all Chromium browsers.

Install from Chrome Web Store →

Web Tool

AOM Validator

Paste or upload your AOM surface or policy JSON and get instant validation against the spec schema.

Open Validator →

SDKs · 4 languages

Agent Kits

Official SDKs for building agents that consume AOM surfaces. Python 3 · Node 18+ · .NET 8 · Java 17. With usage examples.

Go to Downloads →

Open Standard

AOM Spec v0.1.0

Read the normative spec, JSON schemas, and surface examples. Hosted on agentobjectmodel.org.

Read the Spec →

WHY USE THESE TOOLS

Ship faster

Stop guessing at HTML structure. AOM surfaces give agents a contract — validate it once, ship confidently.

Stay in control

automation_policy is yours to set. Agents that respect AOM will follow your rules on every page.

Four SDKs, zero lock-in

Python, Node, .NET, Java — all MIT licensed. Drop AOM into any stack with no vendor dependency.

AUTOMATION POLICY

Set the rules. Agents will follow them.

Every AOM surface ships with an automation_policy. Here's what each level means for your site.

automation_policy: none

Agents are instructed not to automate this surface. No tasks, no actions.

automation_policy: allowed

Agents may read and act, within the constraints you define in your surface JSON.

automation_policy: open

Full access. Agents may read, act, and use everything on this surface freely.

→ This site runs automation_policy: open. What does that mean?