seed ▸ login flow opened 0

Automate behind the login wall.

Sign-in, TOTP and email/SMS OTP, dynamic pages. Writ logs in as you and returns a REST endpoint or MCP tool - on your own authorized accounts.

Automate a login flow See Personas

Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

Authenticated workflow

2FA (TOTP)●

Extract recorddone

✓ Personas + TOTP✓ email/SMS OTP✓ REST + MCP

obs ▸ login wall 1

The problem

The login wall stops ordinary automation

The data and actions you need sit behind a login, and TOTP and email/SMS OTP stop ordinary scripts cold. Even with an account of your own, automating it reliably is the hard part.

The data and actions you need sit behind a login.
TOTP and email/SMS OTP stop ordinary scripts cold.
Dynamic pages break brittle automations.

act ▸ sign in · handle · call 3

How Writ solves it

Sign in, handle the hard cases, call the result

Log in as you Personas hold your own credentials and built-in TOTP plus email/SMS OTP, so a workflow signs in on accounts you control.

Handle the hard cases Verification on your own authenticated accounts, dynamic JS pages, and multi-tab flows are handled the way a person would.

Call the result Expose the authenticated workflow as a REST endpoint and an MCP tool at /v1/{slug}/{path}.

hard ▸ what defeats scripts 9

The hard web

The cases that defeat ordinary scripts

Writ handles them as authorized actions on accounts you control.

✓Login walls
✓TOTP authenticator 2FA
✓Email / SMS OTP codes
✓Verification on your own accounts
✓Dynamic / JS-heavy pages
✓Multi-tab flows

api ▸ endpoint called 42

Example

Sign in, pass 2FA, extract

# Workflow "portal-pull": navigate → fill (login, Persona) → twofa → extract (record)

POST https://api.usewrit.app/v1/portal-pull/run
Authorization: Bearer wt_…
→ { "account": "…", "balance": 1240.00, "as_of": "…" }

A login-gated screen becomes a callable, authenticated endpoint.

auth ▸ your accounts 60

Authorized

Authorized access, by design

Your credentials, your accounts. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use. Writ logs in as you, with your own credentials, on accounts you control - it does not bypass access controls. Secrets live in an encrypted vault; your data stays in your tenant.

Encrypted secrets Security

faq ▸ answered 88

FAQ

Login-gated automation questions

How does it handle 2FA?

Personas carry built-in TOTP and mailbox-OTP handling, so the workflow completes 2FA on your own account.

Is this circumvention?

No. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use. Writ logs in as you, with your own credentials, on accounts you control - it does not bypass access controls.