Read supported pages as structure.
The standard is the destination. Operator is how you get value before anyone adopts it. The shipped adapter reads public HTTP/SSR HTML. It does not execute JavaScript, attach to a signed-in browser or submit forms.
Three steps, in the order that saves the most.
Discover
Before launching anything, probe for a sealed surface, an API document, a feed or a sitemap. If a structured API exists we tell you to call it and charge you nothing further. That is the cheapest possible outcome and it happens often.
Read as structure
Where there is no machine surface, the adapter fetches server-rendered HTML. What your model receives is landmarks, an outline, affordances with stable references, form schemas with their validation rules, and media flagged honestly as unreadable when it carries no alt text. Never a screenshot.
Ask a bounded question
Your agent asks where the quote is, not for the whole page. On our sample that is a median of 67 tokens, against a median of 7 screenshots that a vision agent actually read to answer the same questions — and it comes back with a reference you can inspect or use in a form plan.
Your browser, your sessions, your machine.
A single file that attaches to a Chrome you already have open, reads pages with the same extractor the evidence used, runs the same matcher the hosted endpoint runs, and returns the same shape. Read-only: nothing clicked, no consent accepted, no form submitted, no anti-detection. Download it from /kit/operator-local.mjs.
It needs Chrome started with a remote-debugging port. That port has no authentication: any process on the machine that can reach it can drive the browser and read its cookies. Keep it bound to loopback (the default), run it on a copy of your profile rather than the live one, and close that Chrome when you are done. The runner uses a fresh, signed-out context unless you pass --signed-in, and prints a warning when you do. The extractor runs in an isolated world, so a page cannot lie to it about its own structure. A security reviewer will ask about this; the answer is above rather than in a README.
Browser access remains an unverified extension.
A separate four-site experiment observed different access from a real browser. It did not establish account entitlement, general reliability or production browser support.
The shipped Operator does not attach to authenticated browsers. That transport remains unavailable. We do not sell evasion, we do not defeat bot detection, and we will not solve a CAPTCHA for you. That is a losing arms race and it is somebody else's product.
| Hapag-Lloyd | served |
| CMA CGM | served |
| Palletways | served |
| sennder | served |
Support depends on what the server returns.
A product that claims to help with everything is not a product. These boundaries are published because you will find them anyway, and it is cheaper for both of us if you find them here.
| Interaction | Operator | Why |
|---|---|---|
| Machine-to-machine, structured API | Adds nothing | Discovery routes you to the API. Wrapping a machine-native surface in a page read is pure overhead, and we will tell you so rather than bill you for it. |
| Search and discovery | Partial | Search boxes and comboboxes come back as affordances with references you can inspect. |
| Navigation | Partial | Links carry their target and a reference. Cross-frame is NOT handled — neither implementation reads inside an iframe, and this row used to claim otherwise. |
| Reading structured facts | Partial | Landmarks, outline, content, forms and structured data present in server-returned HTML. Client-rendered content is not evaluated. |
| Form fill and transaction | Partial | Field schemas including native validation rules, and a plan validated against them before anything leaves the server — then act by reference, never by coordinate. We do not submit to a host you have not told us you own, so on a third party this is plan-only. Calling it "full" was wrong: there is no submit tool on the public surface. |
| Media and visual-only content | Adds nothing | An unlabelled image is flagged unreadable rather than guessed at. Vision is genuinely irreplaceable there, and our job is to locate the opaque asset and say so. |
| Spatial, CAPTCHA, canvas | Adds nothing | Pixel space with no semantic structure. We report it and defer. We do not solve CAPTCHAs. |
Metered on machine requests, not seats.
A machine request is one discovery, one structured read or one bounded query. Calls we refuse — a private address, a bad scheme, a rate limit — are never metered, because you should not pay for our own guard rails.
- 1,000 machine requests a month, enforced by the same counter as every tier
- Discovery and bounded query
- Server-rendered transport, hosted
- Community support
- 50,000 machine requests a month, enforced
- Cost receipts on every call
- Server-rendered transport, hosted
- Operator Local: attach to your own Chrome
- 500,000 machine requests a month, enforced
- Priority support
- Operator Local on your own signed-in browser, where the sites already let you in
- Plan-only on third parties; submit stays yours
- Runs inside your perimeter
- Charter operations and audit trail
- 99.9% availability commitment
- Routes consequential actions to your authority layer
Every allowance above is enforced by one counter in the database, and the sandbox key you can issue right now is on it. There is no self-serve billing yet: a paid tier is provisioned by us against a pilot or a contract. Operator is a separate line from the standard, which stays free forever, and from certification against it. See the full pricing architecture.
Evaluate before wider adoption.
An open standard has a cold-start problem: it is worth most when everyone has it, and nobody has it on day one. Operator does not have that problem. It works against sites that will never adopt anything, which makes it suitable for a bounded feasibility evaluation.
And it is the best argument for adoption we have. The pitch to a publisher stops being abstract: publish a documented machine surface so an agent can discover the supported interface and its rules.
Operator reads supported public HTTP/SSR pages and returns form plans. It does not perform consequential actions.
Publishers adopt the standard to get the verified, lean machine fast path — and to stop being scraped.
Future consequential actions require a separate authority and settlement implementation. The public beta exposes structure and plans only.
Try it on your own worst page.
Get a key and point it at the site you most dread automating. It will tell you what it costs, and where it cannot help.