co ▸ about opened 0

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.

Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
ths ▸ the missing api 3
01
The thesis

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.

BeforeNo API
supplier-portal.example.com
Email
Password
After200 OK
curl https://api.usewrit.app/v1/supplier-orders/run \
  -H "Authorization: Bearer wt_…"

{ "status": "success", "orders": 42 }
prm ▸ four promises 7
02
What we believe

Four principles that double as promises.

They shape what we ship and how we charge for it.

Runs on your account, not ours.Writ automates work a person could do by hand in a browser, on sites you are authorized to use, with your own credentials and data. We don't break into anything, and your credentials never leave your control.
You own your data.Extracted data, workflows, and recipes are yours. We don't sell data, and we don't train models on your runs. Tenant isolation and encryption are the default, not an upsell.
Honest, usage-based pricing.A monthly pool of credits, metering by actual running time, a prepaid top-up past the pool, and hard spend caps on by default. Run on your own machine and pay nothing for compute. No surprise bills.
Compliance is a feature.An Acceptable Use Policy we actually enforce, GDPR/DPA tooling, data export and erasure, and encryption by default. Responsible use is a value, not a footnote.

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.

run ▸ record to endpoint 11
03
In one minute

How Writ works.

From a recorded browser session to a callable endpoint that watches a page and acts on change.

01Record or describeCapture a real browser workflow, or tell AI the goal and let it build the steps.
02PublishWrit exposes it as a REST endpoint and an MCP tool, authenticated with wt_ keys.
03RunOn your own machine (free of compute) or our managed cloud (metered by running time).
04Watch and actMonitor any page and fire the workflow the instant it changes.
cap ▸ product surface 15
04
What Writ does

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.

Any site to REST + MCPRecord a workflow once, or describe the goal to AI, and publish it as a callable REST endpoint and an MCP tool your agents can use.
The hard web, handledLogins, two-factor (TOTP and email OTP), and dynamic JavaScript pages, on your own authorized accounts. Personas keep sessions reliable.
Watch, then actMonitor any page, as fast as every 10s on Scale, and fire a workflow in seconds when it changes. Notify across six channels.
Describe it, AI wires itScribe, our AI concierge, opens a browser, finds the page, proposes the selectors, and assembles the whole automation for you to confirm.
Self-healing recipesWhen a selector drifts, Writ heals the target in place. If a run still fails, cloud AI rewrites the recipe. Cloud-only auto-repair.
Local-first, or managedRun free on your own machine with your own AI keys, unbilled, data never leaves. Or hand it to the managed cloud, metered by running time.

AI auto-repair is cloud-only; self-healing targets run everywhere. Local and BYO-AI runs carry no compute charge.

mkt ▸ built then shared 19
05
Marketplace

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.

org ▸ built in the open 23
06
The company

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.

FounderBenjamin Garcia
Legal entity Logiciels Writ · NEQ 2282397514
Registered inQuébec, Canada

Verify it yourself: GitHub · Security architecture · Trust Center · Legal identity