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.

Spec

Two open documents describe what a site can do and how an action runs. Both have JSON Schemas: manifest.schema.json and recipe.schema.json.

the manifest

A site's manifest lists its actions. It has a spec version (orsel.manifest/1), the domain, a version number and the actions. Each action has an id, a name, a description, a typed input schema and output schema, and a risk class: read, write, sensitive, irreversible or financial. It also lists preconditions, postconditions (the checks that decide whether a run succeeded), the auth it needs, how it is made safe to repeat, and rate hints.

the recipe

A recipe says how to run one action. It names the tiers to try, fastest first: api, webmcp, replay, dom, agent. Each tier has its requests or steps and the fields to extract, with timeouts. A recipe also carries canary inputs, the origins it may reach (only the site's own), who published it and how it was made.

signing and status

A recipe is signed with Ed25519 over its canonical JSON (RFC 8785), so it is data and never trusted code. Its status is candidate, verified, degraded, quarantined or revoked, and it moves only when checks pass or fail. A candidate can be run only by the organization that made it.

what a run proves

A run succeeds only when the action's postconditions pass, not because the site answered 200. Every find, run, decision and approval goes into a hash-chained ledger that verify recomputes.