Skip to main content

Agents stall at “check your email to continue.” Sente drives a browser through the login or signup, completes email verification from the account’s own inbox, vaults the credentials, and hands your agent a browser that is already signed in. When a site insists on a human, the run stops and pages one — nothing is worked around.

Free tier, no card. Or start with the Quickstart.

One call

Connect an account your org already owns. No identity to create first — the backing email identity is provisioned for you, derived from the app’s hostname.
Registering a new account is the same shape — sente register <appUrl> / registrations.register({ appUrl }) — and is only for apps whose terms permit it. See Register and Acceptable use.

Get started

Quickstart

From zero to an account your agent can use, by CLI or SDK.

Connect an account you own

Owner-authorized: you supply the credentials once, Sente logs in and keeps it re-loginable.

Register a new account

Sente drives signup under a fresh email — with confirm-before-submit for the final click.

Wait for a verification code

waitForOtp / sente wait --otp — the code is extracted server-side on arrival.

What you can build

Agents that operate your SaaS

Hand an agent a browser already signed in to a vendor portal or dashboard your org owns, as a CDP session or a portable Playwright storageState.

Signups that finish themselves

The “check your email” step is completed from the account’s own inbox — no human copying a six-digit code out of a mailbox.

Fleets of accounts that stay alive

Sessions go stale; Sente re-logs in from the vault plus a fresh code and hands back a session it just confirmed.

Escalation instead of dead ends

CAPTCHAs and SMS codes block the run and page a person with an interactive live view. Nothing is worked around.

Platform

Accounts

The account is the object. created or connected, with credentials and TOTP seeds vaulted — connected credentials write-only.

Runs

One browser job: lifecycle, statuses, and the error codes that stop it.

Webhooks

message.received, run.blocked, run.completed, run.failed — pushed to your endpoint.

Audit trail

Every credential read and session open is recorded and queryable.

API reference

The REST API at https://api.sente.run/v1.

SDKs and CLI

@sente-labs/sdk (TypeScript), sente-sdk (Python), and the sente CLI.

What Sente does not do

Stated up front, because it shapes what you can build:
  • CAPTCHAs and SMS 2FA block the run. Sente does not attempt CAPTCHAs and has no phone numbers. Either one pages a human: the run holds (~10 minutes), a person handles the step in the live view, and the run resumes.
  • SSO-only accounts cannot be connected. Accounts that sign in only via Google/Okta SSO or passkeys have no username and password for Sente to vault.
  • Email-code MFA on connected accounts needs a human, unless the account uses TOTP (Sente computes the code from the vaulted seed) or its notification email was repointed to the Sente address.
  • Registration is terms-gated. Sente registers only where the target’s terms permit it.

Next steps

Security

The credential vault, what the browser agent can and cannot see, and where we are on compliance.

Acceptable use

What we ask of you before pointing a run at someone else’s site.

Limits

Per-org caps on runs, identities, and email, and the 429 codes that report them.

The account's inbox

Listing, reading, sending, and replying from the address behind an account.