actasGet started
ActAs · Identity for AI agents

Papers for your AI agents.

Its own email, logins and 2FA codes. Issued in its name, revocable from your desk.

ActAs gives each agent one identity of its own: an inbox on your domain, a vault for its passwords and keys, and authenticator codes. It signs up, verifies and logs in without borrowing yours, and you decide exactly what it can touch.

Get started See how it works

Pro · US$12/month or US$120/year plus applicable tax · 10 agent identities, one plan

Specimen. Sample agents and a fictional domain.
SCHEDULE AEntitlements

What the papers include.

One identity per agent. Five entitlements, four of them in force today.

  • Its own inbox

    An address on your domain. Receives sign-up and verification email; sends one-to-one replies.

  • Its own vault

    Encrypted passwords, API keys and saved logins, in folders you grant.

  • Its own 2FA codes

    Store the authenticator seed once; the agent asks for the current 6-digit code.

  • Access you control

    Per-permission, per-resource connections. Activity for every action. Revoke in one click.

  • Phone & SMSComing soon

    SMS codes forwarded from a phone you pair, with the same scopes.

THE PROBLEMCase no. 1

Agents stall at “check your email.”

Your agent can fill in the form and click “Sign up”. Then the site sends a code to an inbox it doesn’t have, or asks for a 2FA code from your phone. The task comes back to you, or you hand over your own accounts.

Form 1

Lending it your accounts

  • It can read all of your email, not just the code
  • Passwords and .env files end up pasted into chats
  • Every action looks like you did it
  • No clean way to take the access back
Form 2

Giving it an ActAs identity

  • Its own address, so its mail never mixes with yours
  • Its own vault and 2FA codes, granted folder by folder
  • Activity shows which identity did what
  • Revoke a connection and its next request is refused
PROCEDUREThree steps

From “new agent” to “it handles its own logins.”

Three steps. No queue, no photograph required.

  1. 01Apply

    Create an identity

    Name the agent and give it an address on your domain. Connect Cloudflare and ActAs sets up the DNS, or add the records yourself.

  2. 02Endorse

    Give it what the job needs

    Add logins, API keys and authenticator seeds to vault folders, then grant only those folders and permissions to this identity.

  3. 03Hand over

    Connect your agent

    Download a scoped connection and import it into Claude Code, Codex or your own agent with the CLI or HTTP API. Revoke it whenever you like.

ANNEX BFor developers

Works with the agent you already use.

Anything that can run a command or make an HTTP request can use an ActAs identity: Claude Code, Codex, or your own agent.

  • The server enforces the identity, resource and permission scope on every call.
  • Tokens travel in a header, never in a URL, and are stored only as hashes.
  • A revoked connection is refused on its next request.
CLI & API docs openapi.jsonllms.txt
Example CLI usage
# install the CLI (Node.js 22+) and import one identity's connection
curl -fsSLO https://actas.dev/actas-cli.tgz
npm install -g ./actas-cli.tgz
actas connect ./actas-identity.json

actas identity                 # who am I?
actas resources                # what am I allowed to use?

# read the verification email in its own inbox
actas mail INBOX_ID
actas mail INBOX_ID MESSAGE_ID

# a fresh 6-digit code (needs the totp:code grant)
actas totp code /research/supplier-portal

# run a script with keys, without pasting an .env
actas run --path /research --keys SHOP_API_KEY -- node orders.js
TRAVEL RECORDRecorded, not imagined

Sign up. Verify by email. Log in again tomorrow.

A recorded PyPI run: signup with its own ActAs address, email verification through its inbox, then a fresh-session login with the saved credential.

Animated reconstruction of the recorded steps, not a live screen capture. PyPI used a verification link, not a 6-digit code. No package publishing was demonstrated.

Your browser agent operates the website. Other sites may differ or need a human step.

RECORDED RUN · PYPI · SEPT 27
Replaying…0 / 4
PERMITTED USESix examples

What agents do with papers of their own.

Examples with sample agents. Your browser or coding agent does the work; ActAs supplies the inbox, credentials and codes it is allowed to use.

  • a.

    Sign up and verify accounts

    The agent registers with its own address and reads the verification email itself. Nobody has to forward a code at midnight.

  • b.

    Log back in, with 2FA

    Tomorrow’s session is a new chat, but the identity is the same. It uses the saved login and asks ActAs for a fresh authenticator code.

  • c.

    Use API keys without seeing .env files

    actas run injects the keys a script needs into that one process. Nothing is pasted into the chat.

  • d.

    Reply to a vendor from its own address

    One-to-one replies from the agent’s inbox, with the owner’s send switch, caps and automatic pauses. No bulk or marketing email.

  • e.

    A team of agents, each with boundaries

    Scout gets the Research folder, Builder gets Engineering. A grant never reaches another identity.

  • f.

    See and stop what agents do

    Activity records which identity used which key or inbox. Revoke one connection, or the whole identity.

COMPARATIVE NOTEWhy one identity

An inbox gets the code. An identity finishes the job.

An inbox-only API solves the first email. Then the agent still needs somewhere safe for the password, the 2FA seed and the API key, and you still need a way to scope and revoke it. ActAs puts all of that under one identity.

What the agent needsInbox-only APISharing your accountsActAs
A separate email address per agentYesNoYes
Encrypted vault for its passwords and API keysNoPartlyYes
Authenticator (TOTP) codes without your phoneNoNoYes
Separate permissions: read mail, send, reveal secrets, 2FAPartlyNoYes
Revoke one agent without touching the othersPartlyNoYes
Activity per agent identityPartlyNoYes
SMS codesNoPartlyComing soon
High-volume or bulk sendingYesPartlyNo

“Inbox-only API” means a service that gives agents email inboxes but no vault or authenticator. Features vary by provider. If you need bulk or high-volume email, ActAs is not the right tool.

FEE SCHEDULEOne plan

One plan. Everything included.

Sign in with your email, then subscribe to Pro to create agent identities, inboxes, saved accounts and connections. Payments are processed by Stripe.

  • If a subscription lapses, creation pauses. Your identities, mail and credentials stay readable and exportable, and incoming mail keeps arriving for seven days within the monthly cap. Unpaid workspaces may close after at least 60 days, following owner notices and billing reconciliation.
  • The monthly mail cap is hard, with no metered overage at launch. SES attempts a delivery-failure bounce for mail refused after the cap or payment grace. Revoking an identity frees its slot.

Pro

Monthly or annual

US$12/month

or US$120/year

ActAs Pro: US$12/month or US$120/year, plus applicable tax. Renews automatically every month (or year) at the same price until you cancel. Cancel anytime in ActAs settings or your Link account; you keep access until the end of the paid period. No other fees.

Plus applicable tax. Both billing intervals include the same monthly limits.

  • 10 active agent identities per workspace
  • 5,000 incoming emails stored per calendar month (UTC)
  • One custom domain with optional Cloudflare DNS setup, and an email address on it for each identity
  • Saved accounts and encrypted credentials
  • Scoped, revocable connections, the API and the CLI
Get started
ENQUIRIESCounter 1

Questions, answered plainly.

Something else? Email support@actas.dev.

Q1What is an agent identity?

A named identity for one agent, with its own inbox address, vault folders, authenticator codes and connections. It stays the same when you change models or start a new session.

Q2Which agents does it work with?

Anything that can run a command or make an HTTP request: Claude Code, Codex, or your own agent. The CLI needs Node.js 22 or newer.

Q3Do I need my own domain?

Yes. Each agent gets an address on a domain you own. Pro includes one custom domain. Connect a scoped Cloudflare token and ActAs creates the DNS records, or add them by hand.

Q4Can my agent send email?

One-to-one messages and replies from its own address, once you turn on its send switch. Sending has caps, suppression and automatic pauses. There is no bulk or marketing email, and no attachments, CC or BCC yet.

Q5How are passwords, keys and 2FA seeds stored?

Saved credentials are encrypted with AES-GCM, using a key held outside the database. A connection only receives a secret value if you grant reveal permission. For 2FA, the agent asks for the current code.

Q6What happens when I revoke access?

ActAs refuses the connection’s next request. Revoking cannot recall a value the agent has already received, or sign it out of websites it is already logged into. Rotate those passwords from the vault.

Q7Does ActAs get past CAPTCHAs, phone checks or ID checks?

No. Website rules still apply. When a site needs a human, the agent can prepare a handoff so you do just that one step.

Q8What about phone numbers and SMS codes?

Coming soon. You will be able to pair an Android phone and have SMS codes forwarded to an identity, with the same scopes, activity and revoke.

Q9What happens if my subscription lapses?

Creating new things pauses. Your identities, mail and credentials stay readable and exportable, and incoming mail keeps arriving for seven days within the monthly cap.

Annex CWhat’s included, and what’s available today

What works today, and what doesn’t.

We would rather you know the edges before you build on them.

CapabilityStatusNotes
Persistent agent identitiesWorks todayCreate, name and scope an identity; identity-bound connections can be revoked.
Email address on your own domainWorks todayConnect your domain, then give each agent an address on it. Receive mail and send one-to-one messages with owner permission.
Custom mail domains with Connect CloudflareWorks todayOne custom domain on Pro. Connect a scoped Cloudflare token to create DNS automatically; review and confirm existing MX changes. Manual DNS is also supported.
Read mail in workspace, API and CLIWorks todayConnections need the “read email” permission.
Saved accounts and encrypted credentialsWorks todayStored per identity. Revealing a value to a runtime needs an explicit permission.
Scoped connections and revocationWorks todayChoose read email, write resources and/or reveal secrets, for selected resources in one identity.
Guided signup and login with the CLIDemonstratedYour browser agent does the signing up. Demonstrated on PyPI (Sept 27): signup, email verification and a fresh-session login. Other sites may differ or need a human step.
Files stored under an identityNot availableNot available.
Sending email from an agentWorks todayOne-to-one messages and replies from its own address. Owner control, scoped permission, caps, suppression and automatic pauses; no bulk or marketing.
Phone numbers and SMS codesComing soonComing soon: pair an Android phone and forward SMS codes to an identity, with the same scopes, activity and revoke.
Stored TOTP authenticatorsWorks todayVault authenticators can generate codes for explicitly authorized connections.
Passkeys and identity verificationNot availableNot available. Sites that require these still need a human.
Purchases by agentsNot availableNot available. ActAs does not make payments for your agents.
Annex DHow scoped access works

Give a runtime only what it needs.

Each connection is a revocable credential with three independent choices, enforced by the server rather than by the client.

Permissions

Read email, send email, write resources and reveal secrets are separate. Metadata read is always included. Nothing else is implied.

Resources

Pick specific inboxes, accounts and secrets, or all current and future resources in this one identity. A grant never reaches another identity.

Revocation

Revoke a single connection, or the identity to disable all of its identity-bound connections. Revoked credentials are rejected by ActAs on the next request.

Revocation cannot recall a value a runtime has already received, or end sessions the agent opened on third-party websites. Rotate those at the source.

Annex ESecurity, storage and limits

Built so you can see the boundaries.

  • Encrypted at rest

    Saved credentials use standard AES-GCM encryption with a key held outside the database. Received message contents are encrypted before they are stored. A database-only reader gets neither credential values nor message contents.

  • Hashed, one-time-visible tokens

    Connection tokens are shown once and stored only as hashes. They travel in an authorization header, never in a URL.

  • Authorisation on the server

    Every API call is authenticated and checked on the server against workspace, product, identity, resource and permission. One identity’s connection cannot read another’s mail or secrets.

  • Passwordless sign-in

    Workspace sign-in uses a one-time link emailed to you. It expires in 15 minutes and works once.

  • Activity without contents

    Activity records who performed each action and the result. Secret values, tokens and message contents are kept out of activity and logs.

  • Mail is untrusted input

    Verification links and message text come from third parties. Treat them as untrusted in your agent too.

Limits you should know about

  • ActAs has not been independently audited, and does not yet offer multi-factor sign-in.
  • A runtime you allow to reveal a secret receives it in plaintext. Keep that output out of model context if isolation matters to you; ActAs does not make a model unable to leak what it is shown.
  • Stored values are only as recoverable as the encryption key: if that key were lost, encrypted values could not be read back.
  • The original raw copy of each received message is kept in private cloud storage so delivery problems can be investigated. No fixed retention period has been set for these copies yet. Routing details, such as which address received a message, are not separately encrypted.
  • Provider and website rules still apply: CAPTCHAs, identity checks and human-presence requirements are not bypassed.
APPLYStart with one agent

Give your next agent its own papers.

  1. Sign in with your email. You get a one-time link, no password.
  2. Subscribe to Pro.
  3. Connect your domain, then create an agent and allocate its inbox.
  4. Download a connection and import it with the CLI.
Get started Sign inCLI & API docs

Features and limits above reflect what’s live now and may change as we release.