Agent-readable docs index: /docs/llms.txt. Full docs in one file: /docs/llms-full.txt. Download /docs/docs.zip to grep all markdown files locally.

Concepts

operations

find, read, act, watch, explain, approve, revoke. Scopes: find, read, act:read, act:write, act:sensitive, admin. The act scopes are a ladder (act:sensitive includes act:write includes act:read). Only admin includes everything.

risk classes

read, write, sensitive, irreversible, financial. Policy denies everything above read by default. irreversible and financial need a person to approve even when a rule allows them.

tiers

A recipe lists tier plans fastest first: api (an official API), webmcp (a tool the page registers), replay (first-party requests), dom (a script in a page), agent (an agent, last resort). A failure escalates to the next tier, except where escalating could repeat a write that may already have landed.

success

A run is succeeded only when every postcondition passes. Postconditions are checked against what was observed; a condition with no evidence fails.

explore

A site with no recipe cannot run. explore makes read recipes from a site's public pages with no model involved: it maps the site from the page you give it (the page's links, the home page, and the sitemap), groups pages by shape, proposes actions for each section (a read action per page shape, a list action whose slugs feed it, named pages, search), and the site's POST forms (sign in, sign up, contact, subscribe, as approval-gated actions checked against the form and never submitted), and keeps a read action only if the recipe runs on the pages it fetched and on other inputs. The recipe is signed with a key made for that run, whose private half is discarded, and it stays a candidate that only your organization can run until canaries verify it. Names and descriptions are written from the domain and the path, never from page text, because they reach find.

quarantine

Pages are untrusted. A tool-less extractor reads page text and returns only typed fields that validate against the action's output schema. The planner never sees raw page text.

client-side runs

Logged-in actions run in your own browser (the extension) or locally (the CLI), so your sessions stay with you. Hosted runs are for public pages. Captchas, two-factor prompts, expired sessions, rate limits and payment walls stop the run and hand it to a person.