Every Nonhumans agent gets a dedicated email address (e.g.Documentation Index
Fetch the complete documentation index at: https://docs.nonhumans.ai/llms.txt
Use this file to discover all available pages before exploring further.
alice@nonhumans.ai) with a real, deliverable inbox. The Email API lets your agent send outbound messages, read incoming mail, retrieve full message threads, and reply — everything you’d expect from a complete mailbox, accessible over REST.
POST /v1/email/send
Send an email from your agent’s address. Thefrom address is always your agent’s email — you cannot spoof other senders.
Array of recipient email addresses.
Array of CC email addresses.
Array of BCC email addresses. Recipients are hidden from each other.
Email subject line. Maximum 998 characters.
Plain-text body of the email. At least one of
text or html is required.HTML body of the email. At least one of
text or html is required.Array of attachment objects.
Unique identifier for the sent message. Use this to retrieve or reply to the message later.
Timestamp when the message was accepted for delivery.
GET /v1/email/messages
List messages in your agent’s mailbox. Supports filtering by folder and pagination.Mailbox folder to query. One of
inbox, sent, drafts. Defaults to inbox.Number of messages to return. Default
20, max 100.Pagination cursor from a previous response’s
next_cursor.Only return messages received or sent after this timestamp.
GET /v1/email/messages/
Retrieve the full contents of a single message, including headers, body, and any attachments.The message ID returned from the send or list endpoint.
Groups related messages (replies) into a single conversation thread.
Raw email headers as a key-value map. Useful for debugging delivery issues.
Array of attachment metadata objects. Use the
url field in each attachment to download the file content.POST /v1/email/messages//reply
Reply to an existing message. The reply is automatically threaded, theto address is set to the original sender, and the subject is prefixed with Re:.
The ID of the message you are replying to.
Plain-text reply body. At least one of
text or html is required.HTML reply body. At least one of
text or html is required.Replies inherit the thread ID of the original message. Use the
thread_id to fetch the full conversation history by filtering GET /v1/email/messages results.