For Website Owners
Publish an AOM surface, set your automation_policy, and ship an agent-ready contract your stack can rely on.
WHAT YOU GET
You set the rules
Publish automation_policy: none, allowed, or open. Agents that read AOM will follow what you declare — not guess from your layout.
No HTML changes needed
AOM surfaces are JSON files served alongside your pages. Your frontend stays untouched. Add one route, validate, done.
Versioned and validated
Every surface references a spec version. Run the AOM Validator before shipping so breakage is caught in CI, not in production.
HOW TO GET STARTED
Install Surface Explorer
Inspect any existing page to understand what agents currently see.
Define your first surface
Add a JSON file next to one high-traffic page. Declare tasks, entities, and your automation policy.
Validate before you ship
Paste your JSON into the AOM Validator to confirm it's correctly formed against the spec schema.
Expand to more routes
Once your first surface is live, wire schema validation into your CI pipeline and expand to additional routes.
What a surface looks like
A minimal AOM surface JSON for a homepage. Serve this at your page URL or embed it in a <script type="application/ld+aom+json"> block.
{
"aom_version": "0.1.0",
"surface_id": "homepage",
"url": "https://example.com/",
"automation_policy": "allowed",
"tasks": [
{
"id": "go-to-pricing",
"label": "Navigate to pricing page",
"action": "navigate",
"target": "/pricing"
}
],
"entities": [
{
"id": "site-name",
"type": "text",
"value": "Example Corp"
}
]
}Ready to add AOM to your site?
Download the plugin for your stack — React, Next.js, Vue, static, or server-rendered.