Turn any website
into an API.
Most of the web has no API. Writ makes a login-gated site a callable REST endpoint and MCP tool, run on your own accounts.
The web is the largest API that was never written.
APIs cover a thin slice of the software world. The rest (internal admin panels, supplier portals, government filing systems, legacy tools, anything behind a login) has no API and never will. The standard answer has been brittle scripts that break on the next UI change, or RPA suites built for one-off tasks.
We took a different path: record a real browser workflow once, or describe a goal and let AI build it, and Writ turns it into a stable, callable endpoint at /v1/{slug}/{path} and an MCP tool. It runs the way a person would, on your own account, with your own credentials, so it reaches the authenticated, dynamic web that read-only crawlers can't.
curl https://api.usewrit.app/v1/supplier-orders/run \
-H "Authorization: Bearer wt_…"
{ "status": "success", "orders": 42 } Four principles that double as promises.
They shape what we ship and how we charge for it.
We operate with GDPR-aligned controls, a signed DPA, and encryption by default. A current security review is available on request. See the Trust Center for our current posture.
How Writ works.
From a recorded browser session to a callable endpoint that watches a page and acts on change.
The principle, turned into product.
One idea, run the real web on your own accounts, becomes a small set of capabilities you can lean on.
AI auto-repair is cloud-only; self-healing targets run everywhere. Local and BYO-AI runs carry no compute charge.
Build it. Then share it.
Writ is also a marketplace. Anyone can publish a workflow as a recipe, credentials stripped at publish, and any team can install it and run it on their own account. We see a future where the long tail of "no-API" integrations is built and maintained by the people who need them.
How the cross-tenant path works. Anyone can install a recipe and run it on their own accounts and data. There is no "buy an API key for any listing" flow.
A real company, building in the open.
Writ started from a simple frustration: the tools that should have had APIs didn't, and the workarounds were fragile. We set out to build the missing layer: production-grade, observable, and safe enough to run on real accounts.
We're a focused, developer-led team building in the open about how the platform works, what it costs, and where its limits are.
Verify it yourself: GitHub · Security architecture · Trust Center · Legal identity