Introduction
A real email identity for your agents and applications.
Mailactor gives your application a persistent inbox that can send email, receive replies, and keep a conversation together. Your agent works with a small HTTP API; Mailactor handles email delivery and threading.
Send your first email
Go from your API key to a working inbox and a confirmed delivery.
Explore the API
Find request fields, response schemas, and required permissions.
Start with your organization
Request access with Google or GitHub, then enter your first name, last name, and organization. The team reviews your request before you can use the workspace.
After approval, Mailactor creates your organization and a starter inbox such as first.last@inbox.mailactor.com. If the address is taken, it adds a number. Open API keys in your dashboard to create an agent key. Its secret appears once; save it directly in your secret manager.
Your agent can then create and manage inboxes, send and read messages, reply to conversations, and configure webhooks within the key's permissions.
You do not need to send an organization ID with every request. Your API key identifies the organization and defines what you can access. Start by checking your access.
Four concepts to know
| Resource | What it represents | Keep this value |
|---|---|---|
| Inbox | A persistent email address belonging to your organization. | inbox.id and inbox.address |
| Thread | A conversation inside one inbox. | thread.id |
| Message | One inbound or outbound email in a thread. | message.id |
| Submission | The delivery progress of an outbound email. | submission.id |
Sending from an inbox returns both a message and a submission. The message belongs to a conversation; the submission tells you whether the email reached the recipient's mail server. An accepted API request is not yet a confirmed delivery.
Choose an address
Start with a managed address such as research-agent@inbox.mailactor.com. Mailactor handles its DNS. The starter sending allowance is shared across your organization's managed inboxes.
When you are ready, connect a domain you own, such as agents.example.com. Customer-domain inboxes use your verified domain and do not consume the managed starter allowance; normal traffic limits still apply.
Build your first conversation
- Create an inbox and save its exact address.
- Send a message to a recipient you are authorized to contact.
- Confirm delivery using the returned submission ID.
- Read incoming mail by polling or listening for a webhook.
- Reply to the message and keep the conversation in the same thread.
Current availability
Use the API at https://api.mailactor.com for messages and conversations. The dashboard supports signup, inbox and domain setup, and agent-key creation and revocation. Access approval, permission or organization-policy changes, and full organization erasure still go through the team. There is no human mailbox reader, IMAP, POP3, or WebSocket stream.
Inbound attachment metadata is available, but the current beta blocks downloads of unscanned attachments. See attachments and inbound trust.