For companies

The Work Between Your Systems.

Describe a job once. An agent does it in the web systems you already have — including the ones with no API — while you watch every step, sign off on anything that leaves the company, and keep a record of all of it.

Why it is still done by hand

Most of the work still done by hand in a company is done by hand because the system it lives in has no API — a supplier portal, a council website, an insurer's broker extranet, an internal tool nobody has owned for six years. Integration projects stop at exactly that line. An agent that works a browser does not: if a person can do it in a tab, it can be described once and done the same way every time.

How it goes

Describe the job in your own words. No fields, no flow chart, no integration scoping.
Read back the definition it writes: the steps, the sites, the exact permissions each step may use, and the limits the runtime will enforce.
Watch it run. Every model call and every page it touches is recorded as it happens, and kept.
Sign off on anything that leaves the company. The run stops and shows the exact action, and denying it stops the work rather than pausing it.

What that gets you

It works where the integration stoppedA browser is the one interface every web system has. No API, no vendor roadmap, no export file somebody reformats on a Friday.Live

You watch every stepEvery model call and every page, as it happens and afterwards. A run's record names the exact version of the agent that produced it, and a published version cannot be edited.Live

Reading can never writeWhile an agent is reading it cannot change anything. The rule lifts only inside a sign-in, and inside an action somebody approved — for that site, that action and that amount.Live

Nothing is committed without sign-offThe run stops and shows the exact action before anything leaves the product. Under that sits a second check that does not read the page at all, in case the first one misjudged a button.Live

Every action is loggedRole changes, connections, sign-outs and exports, append-only in the database — the table refuses updates and deletes, so not even an Owner can edit it. Exportable as CSV.Live

Roles decide who may build and who may approveOwner, Editor and Viewer, checked on the server before any page or route reads anything.Live

Rules for the whole workspaceAllowed sites, a default spend cap per agent, and how much needs signing off. The page exists and stores what you set.Stored, not enforced

Paying for something an agent buysAn agent fills the basket and stops at the total. Completing a payment is not built; how it would work is written down and decided.Not built

Running on a scheduleA cadence is part of a definition and the page lists what is queued, but nothing starts a run on a clock yet.Not built

The marks above are not a sales matrix. Each one is checked against the single list the product reads when it has to tell somebody mid-conversation that part of what they asked for will not happen — so a row cannot say Live here while the product says otherwise there. The full list, and how the controls work.

Before you ask

Where it runs: In a web browser, and nowhere else. It cannot touch files on a machine, run a terminal, or use an app installed on a laptop or a phone.
Credentials: A sign-in you add is encrypted and typed only into the one site it belongs to. The model is given a placeholder and never sees it. A site that only offers Continue with Google is handed to a person.
Assurance: There is no SOC 2 report, no external audit and no penetration test. The controls are real; the paperwork around them is not yet. Worth knowing before a procurement conversation rather than during one.
Price: Nothing is charged today. The planned tiers are published and marked as planned.

Talk to us

Tell us the job. The useful version of this conversation starts with something specific that somebody at your company does by hand every week, and which systems it happens in.