Record one browser run, get a deterministic MCP integration for that site.
What it does
Pomerado turns a website into a small, deterministic API instead of leaving an agent to click through it every time. You describe the task in plain language; an agent performs it once against the real site, writing HTTP calls or a Playwright script as it goes, and the finished run is generalized into a repeatable integration that Pomerado exposes over MCP. Later calls replay that recorded path with no model in the loop, which is where the project's 5-30 second figure comes from.
The harness carries guards a browser loop usually lacks: a separate reviewer model checks the building agent's calls against guardrails, synthetic-input tests check the integration is not overfit to the one example, and sign-in runs through a deterministic path so credentials stay out of the model's context, with TOTP seeds stored for two-factor prompts. A maintenance job re-records an integration when a site changes and calls start failing.
The core is MIT-licensed with a hosted offering, and the repo moves daily.