This product was not featured by Product Hunt yet. It will not yet shown by default on their landing page.
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Agent Object Model - The Spec
Open spec for surfaces and AI agents
Agent Object Model (AOM) v0.1.0 is an open standard for AI agents that replaces brittle HTML scraping and guesswork with task-centric, machine-readable surfaces defining what agents can see, do, and safely automate. AOM includes JSON Schemas for surfaces, outputs, and site policies, plus validators and CLIs for developers.
Why: the AI agent angle Today most AI agents see the web through brittle hacks: HTML scraping, ad‑hoc CSS selectors, or screenshots glued together with prompts. A tiny DOM change, an extra banner, or an A/B test can quietly break an entire workflow, and nobody knows until a user hits a bad run.
Every agent framework also invents its own JSON or prompt format for describing tasks, inputs, and outputs. That means agents built on one stack cannot easily interoperate with tools, hosts, or plugins from another. The result is a fragile ecosystem of one‑off integrations instead of a shared language.
Because there’s no standard way to describe surfaces, inputs, outputs, and policies, agents can’t reliably answer basic questions: “What is safe to click?”, “Which actions are allowed here?”, “What is the task‑centric view of this surface?” This is the reliability and safety gap AOM is trying to close.
Why: the website / surface owner angle On the other side, websites are seeing a surge of AI traffic from agents, crawlers, and bots that scrape content without clear permission or constraints. Many major sites have started blocking AI crawlers outright because they lack fine‑grained control over what agents can see, cache, or reuse.
Surface owners are stuck doing custom work for every agent or platform: one JSON shape for integration A, another for B, plus brittle scripts for C. This is expensive, hard to monitor, and breaks whenever the UI evolves. There’s still no standard way to publish “this is the task‑centric view for agents” or to encode “your site, your rules” in a machine‑readable form.
Without that standard, websites either over‑block (no agents allowed) or over‑expose (agents scrape everything and guess the rules). AOM’s goal is to give surface owners a clear way to define how agents should see their site and what they are allowed to do, while giving agents a stable, interoperable view they can trust.
Why: the AI agent angle
Today most AI agents see the web through brittle hacks: HTML scraping, ad‑hoc CSS selectors, or screenshots glued together with prompts. A tiny DOM change, an extra banner, or an A/B test can quietly break an entire workflow, and nobody knows until a user hits a bad run.
Every agent framework also invents its own JSON or prompt format for describing tasks, inputs, and outputs. That means agents built on one stack cannot easily interoperate with tools, hosts, or plugins from another. The result is a fragile ecosystem of one‑off integrations instead of a shared language.
Because there’s no standard way to describe surfaces, inputs, outputs, and policies, agents can’t reliably answer basic questions: “What is safe to click?”, “Which actions are allowed here?”, “What is the task‑centric view of this surface?” This is the reliability and safety gap AOM is trying to close.
Why: the website / surface owner angle
On the other side, websites are seeing a surge of AI traffic from agents, crawlers, and bots that scrape content without clear permission or constraints. Many major sites have started blocking AI crawlers outright because they lack fine‑grained control over what agents can see, cache, or reuse.
Surface owners are stuck doing custom work for every agent or platform: one JSON shape for integration A, another for B, plus brittle scripts for C. This is expensive, hard to monitor, and breaks whenever the UI evolves. There’s still no standard way to publish “this is the task‑centric view for agents” or to encode “your site, your rules” in a machine‑readable form.
Without that standard, websites either over‑block (no agents allowed) or over‑expose (agents scrape everything and guess the rules). AOM’s goal is to give surface owners a clear way to define how agents should see their site and what they are allowed to do, while giving agents a stable, interoperable view they can trust.