agentobjectmodel.org

AOM™ Policy Badges – Usage Guide

The AOM™ policy badges are official visual indicators for the automation_policy field in AOM surfaces.

Badges are optional for UIs (web + mobile).
Agents MUST rely on the JSON automation_policy value as the source of truth.

For logos, badge layout in this directory, and badge-test.html, see README.md.

Badge mapping

Use these badges according to your AOM automation policy:

automation_policy = "forbidden"
- Use the No Automation badge.
automation_policy = "allowed"
- Optionally use the allowed (with guardrails) badge (AOM™ mark).
automation_policy = "open"
- Use the AOM™ Open badge (recommended for public, agent-friendly surfaces).

Canonical asset URLs

Each badge has two canonical assets:

SVG (preferred): crisp at any size, best for modern browsers.
PNG: fallback for environments that don’t support SVG.

No Automation

https://agentobjectmodel.org/static/aom-badges/no-automation/aom-no-automation.png
https://agentobjectmodel.org/static/aom-badges/no-automation/aom-no-automation.svg

Allowed (with guardrails)

https://agentobjectmodel.org/static/aom-badges/allowed/aom-allowed.png
https://agentobjectmodel.org/static/aom-badges/allowed/aom-allowed.svg

AOM™ Open

https://agentobjectmodel.org/static/aom-badges/open/aom-open.png
https://agentobjectmodel.org/static/aom-badges/open/aom-open.svg

You may reference these URLs directly or host copies on your own domain.

How to use (HTML)

No Automation (forbidden)

<img src="https://agentobjectmodel.org/static/aom-badges/no-automation/aom-no-automation.svg"
     alt="No Automation (AOM)" width="48" height="48">

Allowed (with guardrails)

<img src="https://agentobjectmodel.org/static/aom-badges/allowed/aom-allowed.svg"
     alt="Agent automation allowed (with guardrails)" width="48" height="48">

AOM™ Open

<img src="https://agentobjectmodel.org/static/aom-badges/open/aom-open.svg"
     alt="Open automation surface (AOM Open)" width="48" height="48">

Rendering and transparency

Badge SVGs and PNGs have transparent backgrounds. Transparent areas show whatever is behind the image (e.g. your page or card background).

Default: Use the <img> examples above as-is; transparent regions will show the underlying background.
Theme-aware (light/dark): To make the badge visually sit on a specific surface (e.g. a card), set the image’s background to match that surface. Example:

.card img[src*="aom-badges"][src$=".svg"] {
  background: var(--card-bg);   /* or your card/surface color */
  border-radius: 50%;           /* optional: round clip for circular badges */
}

Use a single asset; no need for separate “light” and “dark” badge files.

A theme test and copy-paste template is in this directory: badge-test.html. Open it locally to verify light/dark rendering and reuse the card, theme toggle, and CSS pattern in your own pages.

Mobile / compact usage

For mobile headers or compact UIs, use the same SVG with a smaller size:

<div class="header">
  <h1>Checkout</h1>
  <img src="https://agentobjectmodel.org/static/aom-badges/open/aom-open.svg"
       alt="AOM Open" width="32" height="32">
</div>

You can also place badges near primary actions:

<button class="primary">
  Submit Order
  <img src="https://agentobjectmodel.org/static/aom-badges/allowed/aom-allowed.svg"
       alt="Automation allowed (with guardrails)" width="16" height="16">
</button>

Automation policy vs. badge

Required for agents: the automation_policy field in your AOM JSON.
Optional for humans: the badges above, rendered in your HTML / app UI.

Agents MUST honor automation_policy even if no badge is shown.
Badges are for human reassurance and quick visual scanning.

This site is open source. Improve this page.