The browser engine for agents.
Plasmate compiles HTML into a Semantic Object Model, a structured representation that agents can reason about directly. Output reduction and performance depend on the page, configuration, corpus, and runner.
Benchmark claims retain every attempted input and state the exact successful-sample denominator. Compression is supporting byte evidence, not a universal token, cost, latency, or task-success promise.
Reduced motion is enabled. Background particles are disabled.
Deterministic loopback tasks retain cold/warm cache state, latency, outcomes, and provenance.
Real supervised MCP sessions exercise actions, traces, replay refusal, and failure containment.
Historical v0.5.1 snapshots retain successful, blocked, and failed inputs; byte-ratio samples use explicit denominators. Inspect the evidence.
Byte reduction does not establish token cost or task success. Read the methodology.
The DOM was built for humans
The Document Object Model represents a page as a tree of elements. It includes styling, layout, accessibility attributes, event handlers, and rendering state. All of it.
Agents don't need all of it.
The Semantic Object Model extracts what matters: structure, content, and interactive elements. It's a projection of the DOM optimized for reasoning, not rendering.
DOM
Rendering-oriented tree
SOM
Agent-oriented structure
Measure serialized bytes and tokens on the exact page and configuration you use.
SOM is not lossy compression. It's a different representation for a different purpose.
Seven foundational methods, plus extensions.
Chrome DevTools Protocol has hundreds of methods. Most exist for debugging, profiling, and human-driven inspection.
AWP's foundational v0.1 core has seven wire methods:
The current handler also exposes session listing, network interception, plugin inspection, cookie operations, and proxy-pool extensions. Click, type, select, scroll, toggle, and clear are actions carried by page.act, not additional wire methods.
These are intents, not coordinate instructions. Plasmate handles the implementation; your agent handles the reasoning.
CDP compatibility is included as a legacy bridge. AWP is the native protocol.
Infrastructure, not product
Plasmate is Apache 2.0 licensed. Use it, fork it, embed it, sell it.
SOM and AWP are specifications, not features. We want them implemented everywhere: in other browser engines, in agent frameworks, in production systems we'll never see.
The web has standards for documents, for styling, for scripting. It needs a standard for agents. This is that standard.
Member of the W3C Web Content and Browser AI Community Group. SOM and AWP are being developed as open web standards.
30 seconds. Your AI gets a better browser.
One command. No config files.
claude mcp add plasmate -- npx plasmate-mcp
One command. Skill handles everything.
clawhub install plasmate
Add to your MCP config, restart.
npx plasmate-mcp
For scripts, pipelines, and direct use.
curl -fsSL https://plasmate.app/install.sh | sh
First browser tool on the official MCP Registry. 230 tests passing. 94/98 top sites covered.
No install required
Don't want to run a binary? The SOM Cache is a hosted API that compiles any URL to SOM on demand. Shared CDN, cached results, zero infrastructure on your side.
When multiple agents request the same page, they share a single compilation. Less redundant fetching for publishers, lower latency for agents.
Works with any HTTP client, any language, any agent framework. No API key required for public pages.
Serve SOM alongside HTML
Publishers can pre-compute SOM for their pages and serve it at a well-known endpoint. Agents discover it automatically, just like sitemaps for search engines.
This is the cooperative path: instead of blocking agents or serving them expensive raw HTML, give them a structured format designed for their consumption. Lower bandwidth costs, content control, and provenance metadata for attribution.
Publisher bandwidth and infrastructure impact depends on the source page, cached representation, traffic profile, and delivery stack. Measure both paths before projecting savings. Read the exploratory analysis.
plasmate.app and somordom.com already serve /.well-known/som.json. robots.txt extension proposal in the research papers.
Release status
The v0.6.0 Rust engine and MCP metadata are unreleased. The OCI Registry entry remains unavailable until the immutable, newly labeled v0.6.0 image is built and anonymously pullable. Published SDKs and adapters retain their independent versions.
Performance is workload-specific
The deterministic release benchmark retains build profile, runner, cache state, JavaScript mode, latency, memory high-water mark, and every task outcome. Public-web coverage uses a separate observational schema and preserves blocked, failed, crash, and timeout inputs.
Do not compare debug and release reports, public-network and loopback samples, or different corpus digests as one series. Byte reduction is supporting evidence, not task success. Read the benchmark policy.