Your AI agent gets its own identity.
And real accounts.

Signup ends with an email your agent never gets.

Signup and login flows end with a verification email. If your agent has no inbox of its own, that's where the automation stops. Or worse, it runs on your personal accounts.

The verification inbox for browser agents.

Every inbound email is classified on arrival (OTP, magic link, or other) with the code or link already extracted. Your agent makes one call that blocks until the verification email lands, parsed and ready. Email content is treated as untrusted; extraction is hardened against prompt injection.

$ CODE=$(sente wait --identity support-bot --otp --timeout 60)   # blocks, prints just the code
$ LINK=$(sente wait --identity support-bot --magic-link)         # or just the link
$ echo $CODE
481923

import { Sente } from "@sente-labs/sdk";

const sente = new Sente({ apiKey: process.env.SENTE_API_TOKEN! });

const idt = await sente.identities.create({ name: "support-bot", localPart: "support-bot" });
// -> { id, email: "support-bot@agents.sente.run" }

const since = new Date().toISOString();
// ...trigger the signup / login that sends the verification email...

const otp = await sente.messages.waitForOtp(idt.id, { since, timeout: 60 });
if (otp) console.log(otp.code); // e.g. "481923"

// links instead:
const ml = await sente.messages.waitForMagicLink(idt.id, { since, timeout: 60 });

import os
from sente import Sente
from datetime import datetime, timezone

sente = Sente(api_key=os.environ["SENTE_API_TOKEN"])

idt = sente.identities.create(name="support-bot", local_part="support-bot")
# -> support-bot@agents.sente.run

since = datetime.now(timezone.utc).isoformat()
# ... trigger the app's "send code" action ...

r = sente.messages.wait_for_otp(idt.id, since=since, timeout=60)
if r:
    print(r.code)  # magic links: wait_for_magic_link(...)

A real address your agent owns, not a temp inbox.

Identities live on agents.sente.run, are long-lived, and are reused across apps. Your org owns them; your agent operates them with a scoped API key.

From signup URL to a durable, signed-in account.

Give Sente an app's signup page and an identity. A managed browser registers, the verification code or magic link is picked from the identity's own inbox and applied automatically, and you get back an account that outlives the run: credentials in an encrypted vault, session persisted, re-login on demand.

$ sente register https://app.example.com --identity support-bot
run_01hf…  queued → running → awaiting_verification → running → completed ✓


$ sente credentials reg_01hf…   # vaulted username + password
$ sente relogin reg_01hf…       # fresh signed-in session, anytime

When a run can't proceed (a CAPTCHA, an unexpected step) it doesn't dead-end: it holds, surfaces a live view, and a person can clear the step and resume. Stable error codes tell you exactly why (CAPTCHA_REQUIRED, PHONE_REQUIRED, …).

Human-in-the-loop by design.

Sente is for agents that apps can see and choose to admit. Your org's human owns every identity and account; the agent operates them under delegated, auditable access.

Four commands. That's the whole required interaction.

$ npm i -g @sente-labs/cli
$ sente login                                   # browser sign-in; free tier, no card
$ sente identity create --name "support-bot" --local-part support-bot
→ support-bot@agents.sente.run

$ sente wait --identity support-bot --otp       # blocks, prints just the code

Or skip the terminal: paste give my agent email capabilities via https://sente.run/skill.md into your coding agent and let it do this for you.