Email API for AI agents

Build an agent workflow with email

An agent doing customer support, scheduling or operations needs a stable address and a record of the conversation. Lupin groups incoming messages and replies into threads, so your application can retrieve context and choose the next action without treating every email as a new task.

What the API supports

• Create and manage agent inboxes
• Read messages, threads, attachments and raw MIME
• Prepare drafts, schedule sends and reply in a thread
• Use webhooks and WebSockets for email events
• Connect a custom sending domain with DNS verification

From setup to a verified outcome

1. Create an identity

   Register an agent or connect an existing workspace key, then select an inbox or create one within the workspace allowance.

2. Read before acting

   Subscribe to email events and retrieve the relevant thread, message or attachment using an API key with the required scope.

3. Send with a stable request identity

   Draft a reply and use the documented idempotency key for sending. Check the result rather than repeating a send when its outcome is uncertain.

Availability and limits

• Outbound recipients are restricted until the workspace completes the applicable verification.
• Inbox, recipient, storage and retention allowances depend on the plan. The console and API report the current limits.
• Custom domains require DNS setup; having an agent inbox does not verify another organization’s domain.

Check your workspace for its current configuration, usage and limits. Compare the plans before creating paid resources.

Start with the API reference

The following read endpoint is part of this capability. Authenticate with the relevant workspace key and inspect the documented response and permission requirements.

OpenAPI specification · Email documentation · Agent registration

Common questions