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.
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.
Sign in, handle the hard cases, call the result
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
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.
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.
Where do my credentials live?
In an encrypted secrets vault, scoped to your tenant. Your data stays yours.
Automate the web behind the login
Sign in as you, pass 2FA, and call the authenticated workflow as an API.