Limits & capabilities

GET /v1/me reports your effective organization limits, key restrictions, managed starter usage, and platform caps. Inspect it at the start of an integration and when a policy error occurs.

Managed starter allowance

managedStarter contains limit, used, and remaining. The allowance is lifetime-scoped and shared across your organization's managed inboxes. Deleting messages or creating more inboxes does not reset it.

When exhausted, the API can return configure_customer_domain as the required action. Verified customer-domain inboxes bypass the managed starter allowance but continue to obey normal traffic limits.

Sending and resource limits

organization.sendLimits describes per-minute messages, daily messages, and daily recipients. Domain warm-up and global controls can further restrict sending. Key request-rate limits are distinct from message-send limits.

platformLimits includes recipientsPerMessage, messageContentBytes, inboxes, inboxesPerDomain, domains, and webhookEndpoints. Use those deployment values rather than assuming the broad maximum accepted by a schema is your current allowance.

The default resource allowance is three external domains per organization and five inboxes per domain, with a maximum of 25 inboxes across the organization. These are counts of existing resources, not daily creation allowances. Pending domains and disabled inboxes still count until removed. Your managed starter inbox counts toward your organization's allowance on the shared Mailactor domain; other organizations' inboxes do not.

Choose Request a higher limit in the dashboard and enter the total allowance you need and an explanation of your use case. Each request can add up to three to your current allowance. The same dialog appears when adding a domain or inbox exceeds your current limit. An operator reviews the request; your allowance stays unchanged until approval. Only one request for each limit can await review at a time. Approved allowances appear in your dashboard and in GET /v1/me. An inbox-per-domain increase applies across your organization's domains. Existing resources remain available if an allowance is lowered, but further creation is blocked while at or above it.

Daily sending limits are separate and reset at midnight UTC. The private-beta production caps remain 10 messages and 10 recipients per day per domain and per organization, with one message per minute. Warm-up and global safety controls can reduce these further. Registering extra domains does not multiply the organization allowance.

Available now

Google/GitHub signup with human approval; a managed starter inbox; dashboard agent-key creation and revocation; create/list/read/delete inboxes; send new messages; read threads; reply to exact messages; export and delete mailbox content; register and verify customer domains; configure signed inbound webhooks; inspect delivery; and passively validate addresses.

Still handled by the team

Access approval, custom key permissions, organization policy/limit changes, customer-domain removal, and full organization erasure.

Not currently available

A human mailbox UI, email/password signup, IMAP/POP3, WebSockets, drafts, scheduled sends, arbitrary labels, full-text mailbox search, outbound attachment uploads, or customer-managed attachment scanning. Inbound attachments remain blocked unless their scan state is clean.