agentmail 0.1.8 → 0.1.11

package/dist/llms-full.txt

@@ -2,9 +2,11 @@
 
 > Your starting point for building with the AgentMail API.
 
-<Tip title="Welcome to AgentMail!" icon="fa-solid fa-star">
-  We're excited to have you onboard!
-</Tip>
+<Tip title="Welcome to AgentMail!" icon="fa-solid fa-star" />
+
+<Frame caption="We're excited to have you onboard!">
+  <img src="file:1a083c39-ceed-4591-acaf-4220b54f7913" alt="We're excited to have you onboard!" />
+</Frame>
 
 AgentMail is an API platform for giving AI agents their own inboxes to send, receive, and act upon emails. This allows agents to assume their own identity and communicate via the universal protocol of email with services, people, and other agents.
 
@@ -166,12 +168,10 @@ This guide will walk you through installing the AgentMail SDK, authenticating wi
     If you don't have an account yet, you can sign up directly from the console. Once you're logged in, you'll be able to manage your inboxes, view analytics, and create API keys.
   </Step>
 
-  {" "}
-
   <Step title="Create an API Key">
     Now that you're in the console, you'll need to create an API key to
     authenticate your requests. Navigate to the API Keys section in your console
-    dashboard. ![API Key Creation Screenshot](file:2ed6166f-567f-4666-8c03-00684ce19aa3) Click
+    dashboard. ![API Key Creation Screenshot](file:20e7f82e-4a12-4165-ba99-4b5cff0ac0f5) Click
     "Create New API Key" and give it a descriptive name. Once created, copy the
     API key and store it securely. Create a `.env` file in your project's root
     directory and add your key to it. We recommend using environment variables to
@@ -218,6 +218,16 @@ This guide will walk you through installing the AgentMail SDK, authenticating wi
       print("Inbox created successfully!")
       print(inbox)
 
+      # Send Email
+
+      client.inboxes.messages.send(
+      inbox_id="your-email@example.com",
+      to="contact@agentmail.to",
+      subject="Hello from AgentMail!",
+      text="This is my first email sent with the AgentMail API."
+
+      )
+
       ```
 
       ```typescript title="TypeScript"
@@ -238,7 +248,7 @@ This guide will walk you through installing the AgentMail SDK, authenticating wi
 
         // Send an email from the new inbox
         console.log("Sending email...");
-        await client.inboxes.messages.send(inbox.inbox_id, {
+        await client.inboxes.messages.send(inbox.inboxId, {
           to: "your-email@example.com",
           subject: "Hello from AgentMail!",
           text: "This is my first email sent with the AgentMail API.",
@@ -264,7 +274,7 @@ This guide will walk you through installing the AgentMail SDK, authenticating wi
       python quickstart.py
       ```
 
-      ```bash title="Node"
+      ```bash title="TypeScript"
       npx ts-node quickstart.ts
       ```
     </CodeBlocks>
@@ -312,7 +322,7 @@ Unlike traditional email providers that are designed for human scale, AgentMail
 
 As the diagram below illustrates, your `organization` is the top-level container that holds all your resources. You can provision many `Inboxes` within your `organization`, each with its own `Threads`, `Messages`, and `Attachments`, allowing you to manage a large fleet of agents seamlessly.
 
-<img src="file:5059430e-56d3-4f25-8e53-c039ee07eae3" alt="AgentMail Organizational Hierarchy" />
+<img src="file:17d978ed-f12c-4634-8560-1fe14dfd09a0" alt="AgentMail Organizational Hierarchy" />
 
 <Steps>
   <Step title="Organization">
@@ -347,7 +357,7 @@ As the diagram below illustrates, your `organization` is the top-level container
 
 ## Core Capabilities
 
-Here at AgentMail we've now made an `Inbox` is an API resource, meaning you can perform standard CRUD operations on it. Here are the core capabilities you'll use to manage your `Inboxes`.
+Here at AgentMail we've now made an `Inbox` an API resource, meaning you can perform standard CRUD operations on it. Here are the core capabilities you'll use to manage your `Inboxes`.
 
 <CodeBlocks>
   ```python
@@ -732,7 +742,7 @@ Here is an example of a well-structured and styled HTML header:
 </CodeBlocks>
 
 <Frame caption="Look how pretty this message looks!">
-  <img src="file:c026b6cd-f41d-4bc0-9818-5058474f4b79" alt="rendered css" />
+  <img src="file:c2086bbe-a796-4972-be4d-5e4534c24ca8" alt="rendered css" />
 </Frame>
 
 ## Receiving `Messages`
@@ -1135,7 +1145,7 @@ This is where `Labels` become truly powerful. You can list `Threads`, `Messages`
 
 ## What are `Attachments`?
 
-An `Attachment` is a file that is associated with a `Message`. This can be anything from a PDF invoice to a CSV report or an image(though we don't recommend sending images in the first email sent. We go more into this in the [deliverability section](/deliverability)). Your agents can both send `Attachments` in outgoing `Messages` and process `Attachments` from incoming `Messages`.
+An `Attachment` is a file that is associated with a `Message`. This can be anything from a PDF invoice to a CSV report or an image(though we don't recommend sending images in the first email sent. We go more into this in the [deliverability section](/email-deliverability)). Your agents can both send `Attachments` in outgoing `Messages` and process `Attachments` from incoming `Messages`.
 
 ## Sending `Attachments`
 
@@ -1158,15 +1168,15 @@ To send a file, you include it in an `Attachments` array when sending a `Message
   encoded_content = base64.b64encode(file_content.encode()).decode()
 
   sent_message = client.inboxes.messages.send(
-      inbox_id="reports@agentmail.to",
-      to=["supervisor@example.com"],
-      subject="Q4 Financial Report",
-      text="Please see the attached report.",
-      attachments=[{
-          "content": encoded_content,
-          "filename": "Q4-report.txt",
-          "content_type": "text/plain"
-      }]
+  inbox_id="reports@agentmail.to",
+  to=["supervisor@example.com"],
+  subject="Q4 Financial Report",
+  text="Please see the attached report.",
+  attachments=[{
+  "content": encoded_content,
+  "filename": "Q4-report.txt",
+  "content_type": "text/plain"
+  }]
   )
 
   ```
@@ -1207,15 +1217,15 @@ If you know the `Message` an `Attachment` belongs to, you can retrieve it direct
   attachment_id = "attach_789" # From the message object
 
   file_data = client.inboxes.messages.get_attachment(
-      inbox_id=inbox_id,
-      message_id=message_id,
-      attachment_id=attachment_id
+  inbox_id=inbox_id,
+  message_id=message_id,
+  attachment_id=attachment_id
   )
 
   # Now you can save the file
 
   with open("downloaded_file.pdf", "wb") as f:
-      f.write(file_data)
+  f.write(file_data)
 
   ```
 
@@ -1507,27 +1517,6 @@ Pod: "Marketing-Agent"
 * Explore [Domains](/custom-domains) to set up custom email domains for your pods
 
 
-# Integrations
-
-> Overview of AgentMail's integrations
-
-## Platforms
-
-<CardGroup>
-  <Card title="Replit" icon="fa-solid fa-box-open" href="replit" />
-
-  <Card title="Smithery" icon="fa-solid fa-box-open" href="smithery" />
-</CardGroup>
-
-## Frameworks
-
-<CardGroup>
-  <Card title="Mastra" icon="fa-solid fa-box-open" href="mastra" />
-
-  <Card title="CrewAI" icon="fa-solid fa-box-open" href="crewai" />
-</CardGroup>
-
-
 # Replit
 
 > AgentMail's Replit integration
@@ -1602,6 +1591,7 @@ Below is a collections of prebuilt tools that Replit can use out of the box to s
           .union([z.string(), z.array(z.string())])
           .optional()
           .describe('BCC recipients'),
+      subject: z.string().optional().describe('Subject'),
   })
 
   const ReplyToMessageInput = BaseMessageInput.extend({ messageId: MessageId })
@@ -1739,24 +1729,6 @@ Email is critical to identity and communication on the internet. Much of the con
 These are just a few select verticals, but we have seen AgentMail be effective in automating any email task across every function. If a human does it with email, it can be automated with AgentMail.
 
 
-# Smithery
-
-> AgentMail's Smithery integration
-
-
-
-# Mastra
-
-> AgentMail's Mastra integration
-
-
-
-# CrewAI
-
-> AgentMail's CrewAI integration
-
-
-
 # Guide: Sending & Receiving Email
 
 > A step-by-step guide to the practical workflow of sending initial emails and handling replies to have a full conversation.
@@ -2009,7 +1981,7 @@ Configuring your domain is a three-step process: add the domain via API, copy th
     After creating your domain in the AgentMail Console, click the "Download BIND Zone File" button to get the complete zone file.
 
     <Frame caption="Downloading BIND zone file from AgentMail Console">
-      <img src="file:abd861e7-e3c4-4253-843d-5e1877e84487" alt="Download BIND Zone File from Console" />
+      <img src="file:984a2b44-d86f-47bc-ace2-143e0daf1757" alt="Download BIND Zone File from Console" />
     </Frame>
 
     <Tabs>
@@ -2020,13 +1992,13 @@ Configuring your domain is a three-step process: add the domain via API, copy th
         2. Click **"Import zone file"** in the top right corner
 
         <Frame caption="Importing BIND zone file in AWS Route 53">
-          <img src="file:1381b9e1-8945-463b-8211-f3cb7d8ff390" alt="AWS Route 53 BIND Import" />
+          <img src="file:9647ee70-c593-4daa-a8bf-3079e41ff670" alt="AWS Route 53 BIND Import" />
         </Frame>
 
         3. Paste the CONTENTS of downloaded BIND zone file
 
         <Frame caption="Open the file with text editor and paste the contents. It should look similar to what we have in this image.">
-          <img src="file:a1ec7b55-2283-4e6c-af6f-5bfca7ad00d6" alt="AWS Route 53 BIND Import" />
+          <img src="file:8e5863f4-bee3-42c8-a6fe-60fc89f9b534" alt="AWS Route 53 BIND Import" />
         </Frame>
 
         4. Review the records and click **"Import"**
@@ -2039,13 +2011,13 @@ Configuring your domain is a three-step process: add the domain via API, copy th
         2. Navigate to **DNS > Records**
 
         <Frame caption="This is what the page looks like">
-          <img src="file:ba36964f-3f3e-439c-80f0-c71884757f68" alt="Cloudflare BIND Import" />
+          <img src="file:88185597-fdb9-45aa-a132-7b7284bde354" alt="Cloudflare BIND Import" />
         </Frame>
 
         3. Click **"Import and Export"**
 
         <Frame caption="You should be able to just drop the file in">
-          <img src="file:990c0430-f086-4365-813f-a3b6463d5e07" alt="Cloudflare BIND Import" />
+          <img src="file:7fdc901a-28f8-436a-ad49-d2595e448503" alt="Cloudflare BIND Import" />
         </Frame>
 
         4. Upload the downloaded BIND zone file as is
@@ -2058,13 +2030,13 @@ Configuring your domain is a three-step process: add the domain via API, copy th
         2. Navigate to the **DNS** subtab of the domain you want to send from
 
         <Frame caption="Click on this button!">
-          <img src="file:86a3ef0e-6f6e-4eb3-a721-52c1730f0b49" alt="Porkbun DNS Management" />
+          <img src="file:ad432f5f-3bdd-4e60-ad17-c9129578a975" alt="Porkbun DNS Management" />
         </Frame>
 
         3. Scroll down to the quick upload section
 
         <Frame caption="Upload your BIND zone file here">
-          <img src="file:295db837-0235-4696-b96d-5318f68b49f5" alt="Porkbun Zone File Import" />
+          <img src="file:9a206318-f766-4423-b0aa-3c6f637edb2a" alt="Porkbun Zone File Import" />
         </Frame>
 
         4. Upload the downloaded BIND zone file as is
@@ -2148,7 +2120,7 @@ Configuring your domain is a three-step process: add the domain via API, copy th
               * **Value:** Can directly copy paste the `value` from the API response (e.g., `{random_letters_numbers}.dkim.amazonses.com`).
 
             <Frame caption="Example of adding a CNAME record in Route 53. Notice that AWS already appends the root domain (agentmail.cc) to the end of the name value!">
-              <img src="file:e57473d0-08bd-4ddc-ba64-0ff6c2e49ccc" alt="AWS Route 53 Record Configuration" />
+              <img src="file:1913b0a8-b4bb-4368-b90d-4989059e598a" alt="AWS Route 53 Record Configuration" />
             </Frame>
 
             * **TXT (DMARC/SPF):**
@@ -2583,39 +2555,47 @@ When AgentMail sends a webhook, the payload will have the following structure.
 
 # Webhook Events
 
-> A complete reference of the AgentMail webhook event and its payload.
+As mentioned in the overview, webhooks allow us to create event-driven applications.
 
-When you create a webhook, you subscribe to events from AgentMail. As of now, AgentMail supports a single event type: `message.received`. This event is your primary trigger for all agent-based workflows. We will be adding more event types in the future.
+AgentMail supports multiple event types that allow you to build comprehensive, event-driven workflows for your email agents.
 
 All webhook payloads follow the same basic structure:
 
 ```json
 {
-  "event": "event.name",
-  "data": {
-    // ... event-specific data object
-  }
+  "type": "event",
+  "event_type": "event.name",
+  "event_id": "evt_123abc..."
+  // ... event-specific data object
 }
 ```
 
-## Message Event
-
-The `message.received` event is triggered whenever a new email is successfully received and processed in one of your `Inboxes`.
+## Message Events
 
 ### `message.received`
 
-* **Description:** This is the main trigger to kick off your agent's workflow. Use this event to fetch the full message content, process it, and decide on the next action, such as generating a reply.
-* **Use Case:** Instantly kick off an agent's workflow to process and reply to an incoming email.
+* **Description:** Triggered whenever a new email is successfully received and processed in one of your `Inboxes`. This is the most common trigger to kick off agent workflows.
+* **Example use-case:** Kick off a internal workflow when a customer complaint email hits the support inbox
+
+<Callout>
+  Something here to notice is message.received is the only webhook event that
+  includes both the metadata on the `Thread` and the `Message` in the payload.
+  Other event types send only metadata on the event. Let us know if you need
+  metadata on other event types by emailing `support@agentmail.cc`
+</Callout>
 
 <CodeGroup>
   ```json
   {
-    "event": "message.received",
-    "data": {
-      "id": "msg_123abc",
-      "object": "message",
+    "type": "event",
+    "event_type": "message.received",
+    "event_id": "evt_123abc",
+    "message": {
       "inbox_id": "inbox_456def",
       "thread_id": "thd_789ghi",
+      "message_id": "msg_123abc",
+      "labels": ["received"],
+      "timestamp": "2023-10-27T10:00:00Z",
       "from": [
         {
           "name": "Jane Doe",
@@ -2629,28 +2609,206 @@ The `message.received` event is triggered whenever a new email is successfully r
         }
       ],
       "subject": "Question about my account",
+      "preview": "A short preview of the email text...",
+      "text": "The full text body of the email.",
+      "html": "<html>...</html>",
       "created_at": "2023-10-27T10:00:00Z"
-      // ... and other message properties
+    },
+    "thread": {
+      // ... thread properties
+    }
+  }
+  ```
+</CodeGroup>
+
+### `message.sent`
+
+* **Description:** Triggered when a message is successfully sent from one of your `Inboxes`.
+* **Use Case:** Track outgoing messages, update your database, or trigger follow-up workflows after sending.
+
+<CodeGroup>
+  ```json
+  {
+    "type": "event",
+    "event_type": "message.sent",
+    "event_id": "evt_456def",
+    "send": {
+      "inbox_id": "inbox_456def",
+      "thread_id": "thd_789ghi",
+      "message_id": "msg_123abc",
+      "timestamp": "2023-10-27T10:05:00Z",
+      "recipients": [
+        "recipient@example.com"
+      ]
     }
   }
   ```
 </CodeGroup>
 
-## Future Events
+### `message.delivered`
 
-We are working on expanding our event offerings. In the future, you can expect to see events related to email delivery status, such as:
+* **Description:** Triggered when a sent message is successfully delivered to the recipient's mail server.
+* **Use Case:** Confirm successful delivery, update message status, or trigger delivery confirmation workflows.
 
-* `delivery.success`
-* `delivery.bounced`
-* `delivery.complained`
-* and much more...
+<CodeGroup>
+  ```json
+  {
+    "type": "event",
+    "event_type": "message.delivered",
+    "event_id": "evt_789ghi",
+    "delivery": {
+      "inbox_id": "inbox_456def",
+      "thread_id": "thd_789ghi",
+      "message_id": "msg_123abc",
+      "timestamp": "2023-10-27T10:06:00Z",
+      "recipients": [
+        "recipient@example.com"
+      ]
+    }
+  }
+  ```
+</CodeGroup>
 
-Stay tuned for updates as we roll out these new features!
+<AccordionGroup>
+  <Accordion title="What is the difference between `message.sent` and `message.delivered?`" defaultOpen={true}>
+    `message.sent` means the message has succesfully left our servers and is out
+    to travel the network. This is typically happens before `message.delivered`
+    where `message.delivered` means the recieving email server(whether its Gmail
+    or Outlook) gives us the `200 OK` saying the email has been received. What
+    they do with the email after is unknown.
+  </Accordion>
 
-If you have any specific webhook notifications you would like, please ping us in the `#feature-requests` channel in the [Discord](https://discord.gg/hTYatWYWBc)
+  <Accordion title="Does `message.delivered` mean I landed in their inbox?">
+    Nope. As mentioned `message.delivered` means the receiving email server,
+    whether it's Gmail or Outlook tells us "Hey AgentMail, we got your email,
+    we'll take it from here!". They typically have their own properitary
+    algorithms to determine whether the email is going to end up in the inbox or
+    spam, but rest assured we handle everything needed for providers like Gmail
+    to deem the emails primary inbox worthy
+  </Accordion>
+</AccordionGroup>
 
-```
-```
+### `message.bounced`
+
+* **Description:** Triggered when a sent message fails to deliver and bounces back. Includes bounce type and sub-type information.
+* **Use Case:** Handle bounced emails, update recipient status, or trigger bounce handling workflows.
+
+<CodeGroup>
+  ```json
+  {
+    "type": "event",
+    "event_type": "message.bounced",
+    "event_id": "evt_012jkl",
+    "bounce": {
+      "inbox_id": "inbox_456def",
+      "thread_id": "thd_789ghi",
+      "message_id": "msg_123abc",
+      "timestamp": "2023-10-27T10:07:00Z",
+      "type": "Permanent",
+      "sub_type": "General",
+      "recipients": [
+        {
+          "address": "invalid@example.com",
+          "status": "bounced"
+        }
+      ]
+    }
+  }
+  ```
+</CodeGroup>
+
+### `message.complained`
+
+* **Description:** Triggered when a recipient marks your message as spam or files a complaint.
+* **Use Case:** Handle spam complaints, update sender reputation, or trigger complaint handling workflows.
+
+<CodeGroup>
+  ```json
+  {
+    "type": "event",
+    "event_type": "message.complained",
+    "event_id": "evt_345mno",
+    "complaint": {
+      "inbox_id": "inbox_456def",
+      "thread_id": "thd_789ghi",
+      "message_id": "msg_123abc",
+      "timestamp": "2023-10-27T10:08:00Z",
+      "type": "abuse",
+      "sub_type": "spam",
+      "recipients": [
+        "complainer@example.com"
+      ]
+    }
+  }
+  ```
+</CodeGroup>
+
+### `message.rejected`
+
+* **Description:** Triggered when a message is rejected before being sent, typically due to validation errors or policy violations.
+* **Use Case:** Handle rejected messages, log rejection reasons, or trigger validation workflows.
+
+<CodeGroup>
+  ```json
+  {
+    "type": "event",
+    "event_type": "message.rejected",
+    "event_id": "evt_678pqr",
+    "reject": {
+      "inbox_id": "inbox_456def",
+      "thread_id": "thd_789ghi",
+      "message_id": "msg_123abc",
+      "timestamp": "2023-10-27T10:09:00Z",
+      "reason": "Invalid recipient address"
+    }
+  }
+  ```
+</CodeGroup>
+
+<Warning>
+  If you send an email to a `bounced` address, `rejected` address, or
+  `complained` address we prevent you from sending to this email address ever
+  again to keep bounce rates low. Make sure to keep your account bounce rate
+  under 4%, otherwise we will put your account under review.
+</Warning>
+
+## Domain Events
+
+### `domain.verified`
+
+* **Description:** Triggered when a domain is successfully verified and ready to use for sending emails.
+* **Use Case:** Automatically enable domain-specific features, update domain status, or trigger post-verification workflows.
+
+<CodeGroup>
+  ```json
+  {
+    "type": "event",
+    "event_type": "domain.verified",
+    "event_id": "evt_901stu",
+    "domain": {
+      "domain_id": "dom_123abc",
+      "status": "verified",
+      "feedback_enabled": true,
+      "records": [
+        // ... DNS verification records
+      ],
+      "created_at": "2023-10-27T09:00:00Z",
+      "updated_at": "2023-10-27T10:00:00Z"
+    }
+  }
+  ```
+</CodeGroup>
+
+## Event Filtering
+
+When creating a webhook, you can specify which events to subscribe to. This allows you to:
+
+* Reduce webhook traffic by only subscribing to events you need
+* Create specialized webhooks for specific workflows
+
+For example, if you only need to trigger workflows on incoming messages, you can subscribe to just `message.received`. If you're building a delivery tracking system, you might subscribe to `message.sent`, `message.delivered`, and `message.bounced`.
+
+If you have any specific webhook notifications you would like, please ping us in the `#feature-requests` channel in the [Discord](https://discord.gg/hTYatWYWBc)
 
 
 # Webhook Setup Guide
@@ -2684,13 +2842,13 @@ Ngrok creates a secure tunnel from a public URL to your local development server
 
 Visit [ngrok.com](https://ngrok.com/) and click "Sign up" to create a free account.
 
-<img src="file:b2e9355e-36a9-46dc-bbe0-8192253fc301" alt="Ngrok homepage" />
+<img src="file:c15f82e4-27f6-4a70-ac26-add0b5b12db0" alt="Ngrok homepage" />
 
 ### 1.2 Choose your platform and install
 
 After logging in, ngrok will guide you through the setup process. Select your operating system and follow the installation instructions.
 
-<img src="file:3905deb7-315f-48fe-adee-1f4e4a115bcd" alt="Ngrok setup instructions" />
+<img src="file:4a0b3ee3-7848-45d2-be50-2b5ff7c85295" alt="Ngrok setup instructions" />
 
 For macOS, you can install ngrok via Homebrew:
 
@@ -2736,7 +2894,7 @@ ngrok http 3000
 
 You should see output similar to this:
 
-<img src="file:96fe265e-bc8e-40fc-8bb1-a53acadb74ca" alt="Ngrok terminal output" />
+<img src="file:8bcb8b41-cb1c-462c-8fe4-e9e6a1184d0b" alt="Ngrok terminal output" />
 
 Copy the **Forwarding URL** (e.g., `https://your-subdomain.ngrok-free.app`). This is the public URL that AgentMail will use to send webhooks.
 
@@ -2833,7 +2991,7 @@ python webhook_receiver.py
 
 Open your browser and visit `http://127.0.0.1:3000` to see the status page confirming your webhook receiver is running:
 
-<img src="file:6e602847-1e91-47d2-8aa0-c4d8ca72fed4" alt="Webhook receiver status page" />
+<img src="file:ca0e6f7a-9ed4-4689-9508-7a56cef9eaf5" alt="Webhook receiver status page" />
 
 ## Testing Your Setup
 
@@ -2955,7 +3113,7 @@ How you send your emails is just as important as what you send. If you're sendin
     more natural to email providers. AgentMail's ability to create inboxes at
     scale makes this strategy easy to implement.
 
-    <img src="file:d79176d8-08fb-4eba-b880-66bfcf164f59" alt="Diagram comparing one inbox sending 1000 emails vs. five inboxes sending 200 each." />
+    <img src="file:a620b6d7-d2f7-4925-94ce-afcd6fb2ff4c" alt="Diagram comparing one inbox sending 1000 emails vs. five inboxes sending 200 each." />
   </Step>
 
   <Step title="Protect Your Reputation with Multiple Domains">
@@ -4974,7 +5132,7 @@ Done
 
 Go to your AgentMail inbox and filter by labels to organize your emails:
 
-<img src="file:19536629-9971-42f0-b8c1-ffa1f9849fd5" alt="Test image" />
+<img src="file:2d19dca9-3d2a-43a1-a741-27bc0b88bc19" alt="Test image" />
 
 **Filter by sentiment:**
 
@@ -5796,7 +5954,55 @@ We hope this provides a clear and transparent look into why these DNS records ar
 
 # SOC 2 Compliance
 
-We're almost there....
+> AgentMail's SOC 2 Type II certification and what it means for your data security
+
+AgentMail is **SOC 2 Type II certified**, demonstrating our commitment to maintaining the highest standards of security, availability, and confidentiality for your data.
+
+<img src="file:7e299fb7-9841-4f90-a033-b5e4878067b1" alt="SOC 2 Type II Certified" />
+
+## What is SOC 2?
+
+SOC 2 is a rigorous auditing standard developed by the American Institute of Certified Public Accountants (AICPA). It evaluates how organizations manage customer data based on five principles:
+
+* **Security**: Protection against unauthorized access
+* **Availability**: Systems are operational and accessible as committed
+* **Processing Integrity**: Data processing is complete, accurate, and authorized
+* **Confidentiality**: Information designated as confidential is protected
+* **Privacy**: Personal information is collected, used, and retained appropriately
+
+## What does this mean for you?
+
+When you use AgentMail, you can trust that:
+
+<AccordionGroup>
+  <Accordion title="Your data is protected by enterprise-grade security">
+    We've implemented comprehensive security controls that have been
+    independently verified by third-party auditors. This includes access
+    controls, encryption, and continuous monitoring.
+  </Accordion>
+
+  <Accordion title="We follow industry best practices">
+    Our policies and procedures align with established security frameworks. We
+    don't just claim to be secure—we prove it through regular audits.
+  </Accordion>
+
+  <Accordion title="Our controls are continuously monitored">
+    SOC 2 Type II certification means our controls were tested over an
+    observation period, not just at a single point in time. This demonstrates
+    consistent, ongoing compliance.
+  </Accordion>
+</AccordionGroup>
+
+## Our Certifications
+
+| Certification | Status      | Last Audit    |
+| ------------- | ----------- | ------------- |
+| SOC 2 Type I  | ✅ Compliant | —             |
+| SOC 2 Type II | ✅ Compliant | November 2025 |
+
+## Request Compliance Documentation
+
+Need our SOC 2 report for your vendor assessment? Contact our team at [founders@agentmail.cc](mailto:founders@agentmail.cc) to request access to our compliance documentation.
 
 
 # API Welcome
@@ -5908,9 +6114,11 @@ components:
         updated_at:
           type: string
           format: date-time
+          description: Time at which inbox was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which inbox was created.
       required:
         - pod_id
         - inbox_id
@@ -5929,6 +6137,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_inboxes:Inbox'
+          description: Ordered by `created_at` descending.
       required:
         - count
         - inboxes
@@ -6126,9 +6335,11 @@ components:
         updated_at:
           type: string
           format: date-time
+          description: Time at which inbox was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which inbox was created.
       required:
         - pod_id
         - inbox_id
@@ -6318,8 +6529,12 @@ components:
       properties:
         username:
           type: string
+          description: Username of address. Randomly generated if not specified.
         domain:
           type: string
+          description: >-
+            Domain of address. Must be verified domain. Defaults to
+            `agentmail.to`.
         display_name:
           $ref: '#/components/schemas/type_inboxes:DisplayName'
         client_id:
@@ -6342,9 +6557,11 @@ components:
         updated_at:
           type: string
           format: date-time
+          description: Time at which inbox was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which inbox was created.
       required:
         - pod_id
         - inbox_id
@@ -6363,7 +6580,7 @@ async function main() {
         environment: "https://api.agentmail.to",
         apiKey: "YOUR_TOKEN_HERE",
     });
-    await client.inboxes.create({});
+    await client.inboxes.create();
 }
 main();
 
@@ -6386,7 +6603,6 @@ package main
 
 import (
 	"fmt"
-	"strings"
 	"net/http"
 	"io"
 )
@@ -6395,9 +6611,7 @@ func main() {
 
 	url := "https://api.agentmail.to/v0/inboxes"
 
-	payload := strings.NewReader("{}")
-
-	req, _ := http.NewRequest("POST", url, payload)
+	req, _ := http.NewRequest("POST", url, nil)
 
 	req.Header.Add("Authorization", "Bearer <api_key>")
 	req.Header.Add("Content-Type", "application/json")
@@ -6425,7 +6639,6 @@ http.use_ssl = true
 request = Net::HTTP::Post.new(url)
 request["Authorization"] = 'Bearer <api_key>'
 request["Content-Type"] = 'application/json'
-request.body = "{}"
 
 response = http.request(request)
 puts response.read_body
@@ -6435,7 +6648,6 @@ puts response.read_body
 HttpResponse<String> response = Unirest.post("https://api.agentmail.to/v0/inboxes")
   .header("Authorization", "Bearer <api_key>")
   .header("Content-Type", "application/json")
-  .body("{}")
   .asString();
 ```
 
@@ -6445,7 +6657,6 @@ HttpResponse<String> response = Unirest.post("https://api.agentmail.to/v0/inboxe
 $client = new \GuzzleHttp\Client();
 
 $response = $client->request('POST', 'https://api.agentmail.to/v0/inboxes', [
-  'body' => '{}',
   'headers' => [
     'Authorization' => 'Bearer <api_key>',
     'Content-Type' => 'application/json',
@@ -6460,7 +6671,6 @@ var client = new RestClient("https://api.agentmail.to/v0/inboxes");
 var request = new RestRequest(Method.POST);
 request.AddHeader("Authorization", "Bearer <api_key>");
 request.AddHeader("Content-Type", "application/json");
-request.AddParameter("application/json", "{}", ParameterType.RequestBody);
 IRestResponse response = client.Execute(request);
 ```
 
@@ -6471,16 +6681,12 @@ let headers = [
   "Authorization": "Bearer <api_key>",
   "Content-Type": "application/json"
 ]
-let parameters = [] as [String : Any]
-
-let postData = JSONSerialization.data(withJSONObject: parameters, options: [])
 
 let request = NSMutableURLRequest(url: NSURL(string: "https://api.agentmail.to/v0/inboxes")! as URL,
                                         cachePolicy: .useProtocolCachePolicy,
                                     timeoutInterval: 10.0)
 request.httpMethod = "POST"
 request.allHTTPHeaderFields = headers
-request.httpBody = postData as Data
 
 let session = URLSession.shared
 let dataTask = session.dataTask(with: request as URLRequest, completionHandler: { (data, response, error) -> Void in
@@ -6576,9 +6782,11 @@ components:
         updated_at:
           type: string
           format: date-time
+          description: Time at which inbox was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which inbox was created.
       required:
         - pod_id
         - inbox_id
@@ -7137,6 +7345,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_threads:ThreadItem'
+          description: Ordered by `timestamp` descending.
       required:
         - count
         - threads
@@ -7460,6 +7669,9 @@ components:
           type: array
           items:
             type: string
+          description: >-
+            Reply-to addresses. In format `username@domain.com` or `Display Name
+            <username@domain.com>`.
         to:
           $ref: '#/components/schemas/type_messages:MessageTo'
         cc:
@@ -7474,6 +7686,12 @@ components:
           $ref: '#/components/schemas/type_messages:MessageText'
         html:
           $ref: '#/components/schemas/type_messages:MessageHtml'
+        extracted_text:
+          type: string
+          description: Extracted new text content.
+        extracted_html:
+          type: string
+          description: Extracted new HTML content.
         attachments:
           $ref: '#/components/schemas/type_messages:MessageAttachments'
         in_reply_to:
@@ -7536,6 +7754,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_messages:Message'
+          description: Messages in thread. Ordered by `timestamp` ascending.
       required:
         - inbox_id
         - thread_id
@@ -8287,6 +8506,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_messages:MessageItem'
+          description: Ordered by `timestamp` descending.
       required:
         - count
         - messages
@@ -8569,6 +8789,9 @@ components:
           type: array
           items:
             type: string
+          description: >-
+            Reply-to addresses. In format `username@domain.com` or `Display Name
+            <username@domain.com>`.
         to:
           $ref: '#/components/schemas/type_messages:MessageTo'
         cc:
@@ -8583,6 +8806,12 @@ components:
           $ref: '#/components/schemas/type_messages:MessageText'
         html:
           $ref: '#/components/schemas/type_messages:MessageHtml'
+        extracted_text:
+          type: string
+          description: Extracted new text content.
+        extracted_html:
+          type: string
+          description: Extracted new HTML content.
         attachments:
           $ref: '#/components/schemas/type_messages:MessageAttachments'
         in_reply_to:
@@ -9777,10 +10006,12 @@ components:
           type: array
           items:
             type: string
+          description: Labels to add to message.
         remove_labels:
           type: array
           items:
             type: string
+          description: Labels to remove from message.
     type_threads:ThreadId:
       type: string
     type_messages:MessageLabels:
@@ -9876,6 +10107,9 @@ components:
           type: array
           items:
             type: string
+          description: >-
+            Reply-to addresses. In format `username@domain.com` or `Display Name
+            <username@domain.com>`.
         to:
           $ref: '#/components/schemas/type_messages:MessageTo'
         cc:
@@ -9890,6 +10124,12 @@ components:
           $ref: '#/components/schemas/type_messages:MessageText'
         html:
           $ref: '#/components/schemas/type_messages:MessageHtml'
+        extracted_text:
+          type: string
+          description: Extracted new text content.
+        extracted_html:
+          type: string
+          description: Extracted new HTML content.
         attachments:
           $ref: '#/components/schemas/type_messages:MessageAttachments'
         in_reply_to:
@@ -10273,6 +10513,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_drafts:DraftItem'
+          description: Ordered by `updated_at` descending.
       required:
         - count
         - drafts
@@ -10574,6 +10815,7 @@ components:
           type: array
           items:
             type: string
+          description: IDs of previous messages in thread.
         send_status:
           $ref: '#/components/schemas/type_drafts:DraftSendStatus'
         send_at:
@@ -10583,6 +10825,7 @@ components:
         created_at:
           type: string
           format: date-time
+          description: Time at which draft was created.
       required:
         - inbox_id
         - thread_id
@@ -10915,6 +11158,7 @@ components:
           type: array
           items:
             type: string
+          description: IDs of previous messages in thread.
         send_status:
           $ref: '#/components/schemas/type_drafts:DraftSendStatus'
         send_at:
@@ -10924,6 +11168,7 @@ components:
         created_at:
           type: string
           format: date-time
+          description: Time at which draft was created.
       required:
         - inbox_id
         - thread_id
@@ -11273,6 +11518,7 @@ components:
           type: array
           items:
             type: string
+          description: IDs of previous messages in thread.
         send_status:
           $ref: '#/components/schemas/type_drafts:DraftSendStatus'
         send_at:
@@ -11282,6 +11528,7 @@ components:
         created_at:
           type: string
           format: date-time
+          description: Time at which draft was created.
       required:
         - inbox_id
         - thread_id
@@ -11512,10 +11759,12 @@ components:
           type: array
           items:
             type: string
+          description: Labels to add to message.
         remove_labels:
           type: array
           items:
             type: string
+          description: Labels to remove from message.
     type_messages:MessageId:
       type: string
     type_threads:ThreadId:
@@ -11956,35 +12205,43 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_metrics:MetricTimestamp'
+          description: Timestamps when messages were sent.
         delivered:
           type: array
           items:
             $ref: '#/components/schemas/type_metrics:MetricTimestamp'
+          description: Timestamps when messages were delivered.
         bounced:
           type: array
           items:
             $ref: '#/components/schemas/type_metrics:MetricTimestamp'
+          description: Timestamps when messages bounced.
         delayed:
           type: array
           items:
             $ref: '#/components/schemas/type_metrics:MetricTimestamp'
+          description: Timestamps when messages were delayed.
         rejected:
           type: array
           items:
             $ref: '#/components/schemas/type_metrics:MetricTimestamp'
+          description: Timestamps when messages were rejected.
         complained:
           type: array
           items:
             $ref: '#/components/schemas/type_metrics:MetricTimestamp'
+          description: Timestamps when messages received complaints.
         received:
           type: array
           items:
             $ref: '#/components/schemas/type_metrics:MetricTimestamp'
+          description: Timestamps when messages were received.
     type_metrics:ListMetricsResponse:
       type: object
       properties:
         message:
           $ref: '#/components/schemas/type_metrics:MessageMetrics'
+          description: Message metrics grouped by event type.
 
 ```
 
@@ -12342,6 +12599,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_threads:ThreadItem'
+          description: Ordered by `timestamp` descending.
       required:
         - count
         - threads
@@ -12657,6 +12915,9 @@ components:
           type: array
           items:
             type: string
+          description: >-
+            Reply-to addresses. In format `username@domain.com` or `Display Name
+            <username@domain.com>`.
         to:
           $ref: '#/components/schemas/type_messages:MessageTo'
         cc:
@@ -12671,6 +12932,12 @@ components:
           $ref: '#/components/schemas/type_messages:MessageText'
         html:
           $ref: '#/components/schemas/type_messages:MessageHtml'
+        extracted_text:
+          type: string
+          description: Extracted new text content.
+        extracted_html:
+          type: string
+          description: Extracted new HTML content.
         attachments:
           $ref: '#/components/schemas/type_messages:MessageAttachments'
         in_reply_to:
@@ -12733,6 +13000,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_messages:Message'
+          description: Messages in thread. Ordered by `timestamp` ascending.
       required:
         - inbox_id
         - thread_id
@@ -13267,6 +13535,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_drafts:DraftItem'
+          description: Ordered by `updated_at` descending.
       required:
         - count
         - drafts
@@ -13560,6 +13829,7 @@ components:
           type: array
           items:
             type: string
+          description: IDs of previous messages in thread.
         send_status:
           $ref: '#/components/schemas/type_drafts:DraftSendStatus'
         send_at:
@@ -13569,6 +13839,7 @@ components:
         created_at:
           type: string
           format: date-time
+          description: Time at which draft was created.
       required:
         - inbox_id
         - thread_id
@@ -13780,9 +14051,11 @@ components:
         updated_at:
           type: string
           format: date-time
+          description: Time at which the domain was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which the domain was created.
       required:
         - domain_id
         - feedback_enabled
@@ -13801,6 +14074,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_domains:DomainItem'
+          description: Ordered by `created_at` descending.
       required:
         - count
         - domains
@@ -14004,14 +14278,19 @@ components:
       properties:
         type:
           $ref: '#/components/schemas/type_domains:RecordType'
+          description: The type of the DNS record.
         name:
           type: string
+          description: The name or host of the record.
         value:
           type: string
+          description: The value of the record.
         status:
           $ref: '#/components/schemas/type_domains:RecordStatus'
+          description: The verification status of this specific record.
         priority:
           type: integer
+          description: The priority of the MX record.
       required:
         - type
         - name
@@ -14028,20 +14307,24 @@ components:
           $ref: '#/components/schemas/type_domains:DomainId'
         status:
           $ref: '#/components/schemas/type_domains:VerificationStatus'
+          description: The verification status of the domain.
         feedback_enabled:
           $ref: '#/components/schemas/type_domains:FeedbackEnabled'
         records:
           type: array
           items:
             $ref: '#/components/schemas/type_domains:VerificationRecord'
+          description: A list of DNS records required to verify the domain.
         client_id:
           $ref: '#/components/schemas/type_domains:ClientId'
         updated_at:
           type: string
           format: date-time
+          description: Time at which the domain was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which the domain was created.
       required:
         - domain_id
         - status
@@ -14441,14 +14724,19 @@ components:
       properties:
         type:
           $ref: '#/components/schemas/type_domains:RecordType'
+          description: The type of the DNS record.
         name:
           type: string
+          description: The name or host of the record.
         value:
           type: string
+          description: The value of the record.
         status:
           $ref: '#/components/schemas/type_domains:RecordStatus'
+          description: The verification status of this specific record.
         priority:
           type: integer
+          description: The priority of the MX record.
       required:
         - type
         - name
@@ -14465,20 +14753,24 @@ components:
           $ref: '#/components/schemas/type_domains:DomainId'
         status:
           $ref: '#/components/schemas/type_domains:VerificationStatus'
+          description: The verification status of the domain.
         feedback_enabled:
           $ref: '#/components/schemas/type_domains:FeedbackEnabled'
         records:
           type: array
           items:
             $ref: '#/components/schemas/type_domains:VerificationRecord'
+          description: A list of DNS records required to verify the domain.
         client_id:
           $ref: '#/components/schemas/type_domains:ClientId'
         updated_at:
           type: string
           format: date-time
+          description: Time at which the domain was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which the domain was created.
       required:
         - domain_id
         - status
@@ -15078,14 +15370,18 @@ components:
           $ref: '#/components/schemas/type_webhooks:InboxIds'
         secret:
           type: string
+          description: Secret for webhook signature verification.
         enabled:
           type: boolean
+          description: Whether the webhook is enabled.
         updated_at:
           type: string
           format: date-time
+          description: Time at which webhook was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which webhook was created.
         client_id:
           $ref: '#/components/schemas/type_webhooks:ClientId'
       required:
@@ -15108,6 +15404,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_webhooks:Webhook'
+          description: Ordered by `created_at` descending.
       required:
         - count
         - webhooks
@@ -15320,14 +15617,18 @@ components:
           $ref: '#/components/schemas/type_webhooks:InboxIds'
         secret:
           type: string
+          description: Secret for webhook signature verification.
         enabled:
           type: boolean
+          description: Whether the webhook is enabled.
         updated_at:
           type: string
           format: date-time
+          description: Time at which webhook was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which webhook was created.
         client_id:
           $ref: '#/components/schemas/type_webhooks:ClientId'
       required:
@@ -15563,14 +15864,18 @@ components:
           $ref: '#/components/schemas/type_webhooks:InboxIds'
         secret:
           type: string
+          description: Secret for webhook signature verification.
         enabled:
           type: boolean
+          description: Whether the webhook is enabled.
         updated_at:
           type: string
           format: date-time
+          description: Time at which webhook was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which webhook was created.
         client_id:
           $ref: '#/components/schemas/type_webhooks:ClientId'
       required:
@@ -16072,6 +16377,9 @@ components:
           type: array
           items:
             type: string
+          description: >-
+            Reply-to addresses. In format `username@domain.com` or `Display Name
+            <username@domain.com>`.
         to:
           $ref: '#/components/schemas/type_messages:MessageTo'
         cc:
@@ -16086,6 +16394,12 @@ components:
           $ref: '#/components/schemas/type_messages:MessageText'
         html:
           $ref: '#/components/schemas/type_messages:MessageHtml'
+        extracted_text:
+          type: string
+          description: Extracted new text content.
+        extracted_html:
+          type: string
+          description: Extracted new HTML content.
         attachments:
           $ref: '#/components/schemas/type_messages:MessageAttachments'
         in_reply_to:
@@ -16109,6 +16423,96 @@ components:
         - size
         - updated_at
         - created_at
+    type_threads:ThreadLabels:
+      type: array
+      items:
+        type: string
+    type_threads:ThreadTimestamp:
+      type: string
+      format: date-time
+    type_threads:ThreadReceivedTimestamp:
+      type: string
+      format: date-time
+    type_threads:ThreadSentTimestamp:
+      type: string
+      format: date-time
+    type_threads:ThreadSenders:
+      type: array
+      items:
+        type: string
+    type_threads:ThreadRecipients:
+      type: array
+      items:
+        type: string
+    type_threads:ThreadSubject:
+      type: string
+    type_threads:ThreadPreview:
+      type: string
+    type_threads:ThreadAttachments:
+      type: array
+      items:
+        $ref: '#/components/schemas/type_attachments:Attachment'
+    type_threads:ThreadLastMessageId:
+      type: string
+    type_threads:ThreadMessageCount:
+      type: integer
+    type_threads:ThreadSize:
+      type: integer
+    type_threads:ThreadUpdatedAt:
+      type: string
+      format: date-time
+    type_threads:ThreadCreatedAt:
+      type: string
+      format: date-time
+    type_threads:ThreadItem:
+      type: object
+      properties:
+        inbox_id:
+          $ref: '#/components/schemas/type_inboxes:InboxId'
+        thread_id:
+          $ref: '#/components/schemas/type_threads:ThreadId'
+        labels:
+          $ref: '#/components/schemas/type_threads:ThreadLabels'
+        timestamp:
+          $ref: '#/components/schemas/type_threads:ThreadTimestamp'
+        received_timestamp:
+          $ref: '#/components/schemas/type_threads:ThreadReceivedTimestamp'
+        sent_timestamp:
+          $ref: '#/components/schemas/type_threads:ThreadSentTimestamp'
+        senders:
+          $ref: '#/components/schemas/type_threads:ThreadSenders'
+        recipients:
+          $ref: '#/components/schemas/type_threads:ThreadRecipients'
+        subject:
+          $ref: '#/components/schemas/type_threads:ThreadSubject'
+        preview:
+          $ref: '#/components/schemas/type_threads:ThreadPreview'
+        attachments:
+          $ref: '#/components/schemas/type_threads:ThreadAttachments'
+        last_message_id:
+          $ref: '#/components/schemas/type_threads:ThreadLastMessageId'
+        message_count:
+          $ref: '#/components/schemas/type_threads:ThreadMessageCount'
+        size:
+          $ref: '#/components/schemas/type_threads:ThreadSize'
+        updated_at:
+          $ref: '#/components/schemas/type_threads:ThreadUpdatedAt'
+        created_at:
+          $ref: '#/components/schemas/type_threads:ThreadCreatedAt'
+      required:
+        - inbox_id
+        - thread_id
+        - labels
+        - timestamp
+        - received_timestamp
+        - sent_timestamp
+        - senders
+        - recipients
+        - last_message_id
+        - message_count
+        - size
+        - updated_at
+        - created_at
     type_events:MessageReceivedEvent:
       type: object
       properties:
@@ -16126,11 +16530,14 @@ components:
           $ref: '#/components/schemas/type_events:EventId'
         message:
           $ref: '#/components/schemas/type_messages:Message'
+        thread:
+          $ref: '#/components/schemas/type_threads:ThreadItem'
       required:
         - type
         - event_type
         - event_id
         - message
+        - thread
 
 ```
 
@@ -16213,6 +16620,7 @@ components:
           type: array
           items:
             type: string
+          description: Sent recipients.
       required:
         - inbox_id
         - thread_id
@@ -16323,6 +16731,7 @@ components:
           type: array
           items:
             type: string
+          description: Delivered recipients.
       required:
         - inbox_id
         - thread_id
@@ -16423,8 +16832,10 @@ components:
       properties:
         address:
           type: string
+          description: Recipient address.
         status:
           type: string
+          description: Recipient status.
       required:
         - address
         - status
@@ -16441,12 +16852,15 @@ components:
           $ref: '#/components/schemas/type_events:Timestamp'
         type:
           type: string
+          description: Bounce type.
         sub_type:
           type: string
+          description: Bounce sub-type.
         recipients:
           type: array
           items:
             $ref: '#/components/schemas/type_events:Recipient'
+          description: Bounced recipients.
       required:
         - inbox_id
         - thread_id
@@ -16557,12 +16971,15 @@ components:
           $ref: '#/components/schemas/type_events:Timestamp'
         type:
           type: string
+          description: Complaint type.
         sub_type:
           type: string
+          description: Complaint sub-type.
         recipients:
           type: array
           items:
             type: string
+          description: Complained recipients.
       required:
         - inbox_id
         - thread_id
@@ -16673,6 +17090,7 @@ components:
           $ref: '#/components/schemas/type_events:Timestamp'
         reason:
           type: string
+          description: Reject reason.
       required:
         - inbox_id
         - thread_id
@@ -16787,14 +17205,19 @@ components:
       properties:
         type:
           $ref: '#/components/schemas/type_domains:RecordType'
+          description: The type of the DNS record.
         name:
           type: string
+          description: The name or host of the record.
         value:
           type: string
+          description: The value of the record.
         status:
           $ref: '#/components/schemas/type_domains:RecordStatus'
+          description: The verification status of this specific record.
         priority:
           type: integer
+          description: The priority of the MX record.
       required:
         - type
         - name
@@ -16811,20 +17234,24 @@ components:
           $ref: '#/components/schemas/type_domains:DomainId'
         status:
           $ref: '#/components/schemas/type_domains:VerificationStatus'
+          description: The verification status of the domain.
         feedback_enabled:
           $ref: '#/components/schemas/type_domains:FeedbackEnabled'
         records:
           type: array
           items:
             $ref: '#/components/schemas/type_domains:VerificationRecord'
+          description: A list of DNS records required to verify the domain.
         client_id:
           $ref: '#/components/schemas/type_domains:ClientId'
         updated_at:
           type: string
           format: date-time
+          description: Time at which the domain was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which the domain was created.
       required:
         - domain_id
         - status
@@ -16978,10 +17405,12 @@ components:
           type: array
           items:
             type: string
+          description: IDs of the inboxes that have been subscribed to.
         pod_ids:
           type: array
           items:
             type: string
+          description: IDs of the pods that have been subscribed to.
       required:
         - type
     type_events:EventId:
@@ -17085,6 +17514,9 @@ components:
           type: array
           items:
             type: string
+          description: >-
+            Reply-to addresses. In format `username@domain.com` or `Display Name
+            <username@domain.com>`.
         to:
           $ref: '#/components/schemas/type_messages:MessageTo'
         cc:
@@ -17099,6 +17531,12 @@ components:
           $ref: '#/components/schemas/type_messages:MessageText'
         html:
           $ref: '#/components/schemas/type_messages:MessageHtml'
+        extracted_text:
+          type: string
+          description: Extracted new text content.
+        extracted_html:
+          type: string
+          description: Extracted new HTML content.
         attachments:
           $ref: '#/components/schemas/type_messages:MessageAttachments'
         in_reply_to:
@@ -17122,6 +17560,96 @@ components:
         - size
         - updated_at
         - created_at
+    type_threads:ThreadLabels:
+      type: array
+      items:
+        type: string
+    type_threads:ThreadTimestamp:
+      type: string
+      format: date-time
+    type_threads:ThreadReceivedTimestamp:
+      type: string
+      format: date-time
+    type_threads:ThreadSentTimestamp:
+      type: string
+      format: date-time
+    type_threads:ThreadSenders:
+      type: array
+      items:
+        type: string
+    type_threads:ThreadRecipients:
+      type: array
+      items:
+        type: string
+    type_threads:ThreadSubject:
+      type: string
+    type_threads:ThreadPreview:
+      type: string
+    type_threads:ThreadAttachments:
+      type: array
+      items:
+        $ref: '#/components/schemas/type_attachments:Attachment'
+    type_threads:ThreadLastMessageId:
+      type: string
+    type_threads:ThreadMessageCount:
+      type: integer
+    type_threads:ThreadSize:
+      type: integer
+    type_threads:ThreadUpdatedAt:
+      type: string
+      format: date-time
+    type_threads:ThreadCreatedAt:
+      type: string
+      format: date-time
+    type_threads:ThreadItem:
+      type: object
+      properties:
+        inbox_id:
+          $ref: '#/components/schemas/type_inboxes:InboxId'
+        thread_id:
+          $ref: '#/components/schemas/type_threads:ThreadId'
+        labels:
+          $ref: '#/components/schemas/type_threads:ThreadLabels'
+        timestamp:
+          $ref: '#/components/schemas/type_threads:ThreadTimestamp'
+        received_timestamp:
+          $ref: '#/components/schemas/type_threads:ThreadReceivedTimestamp'
+        sent_timestamp:
+          $ref: '#/components/schemas/type_threads:ThreadSentTimestamp'
+        senders:
+          $ref: '#/components/schemas/type_threads:ThreadSenders'
+        recipients:
+          $ref: '#/components/schemas/type_threads:ThreadRecipients'
+        subject:
+          $ref: '#/components/schemas/type_threads:ThreadSubject'
+        preview:
+          $ref: '#/components/schemas/type_threads:ThreadPreview'
+        attachments:
+          $ref: '#/components/schemas/type_threads:ThreadAttachments'
+        last_message_id:
+          $ref: '#/components/schemas/type_threads:ThreadLastMessageId'
+        message_count:
+          $ref: '#/components/schemas/type_threads:ThreadMessageCount'
+        size:
+          $ref: '#/components/schemas/type_threads:ThreadSize'
+        updated_at:
+          $ref: '#/components/schemas/type_threads:ThreadUpdatedAt'
+        created_at:
+          $ref: '#/components/schemas/type_threads:ThreadCreatedAt'
+      required:
+        - inbox_id
+        - thread_id
+        - labels
+        - timestamp
+        - received_timestamp
+        - sent_timestamp
+        - senders
+        - recipients
+        - last_message_id
+        - message_count
+        - size
+        - updated_at
+        - created_at
     type_events:MessageReceivedEvent:
       type: object
       properties:
@@ -17139,11 +17667,14 @@ components:
           $ref: '#/components/schemas/type_events:EventId'
         message:
           $ref: '#/components/schemas/type_messages:Message'
+        thread:
+          $ref: '#/components/schemas/type_threads:ThreadItem'
       required:
         - type
         - event_type
         - event_id
         - message
+        - thread
     type_events:Timestamp:
       type: string
       format: date-time
@@ -17162,6 +17693,7 @@ components:
           type: array
           items:
             type: string
+          description: Sent recipients.
       required:
         - inbox_id
         - thread_id
@@ -17205,6 +17737,7 @@ components:
           type: array
           items:
             type: string
+          description: Delivered recipients.
       required:
         - inbox_id
         - thread_id
@@ -17238,8 +17771,10 @@ components:
       properties:
         address:
           type: string
+          description: Recipient address.
         status:
           type: string
+          description: Recipient status.
       required:
         - address
         - status
@@ -17256,12 +17791,15 @@ components:
           $ref: '#/components/schemas/type_events:Timestamp'
         type:
           type: string
+          description: Bounce type.
         sub_type:
           type: string
+          description: Bounce sub-type.
         recipients:
           type: array
           items:
             $ref: '#/components/schemas/type_events:Recipient'
+          description: Bounced recipients.
       required:
         - inbox_id
         - thread_id
@@ -17305,12 +17843,15 @@ components:
           $ref: '#/components/schemas/type_events:Timestamp'
         type:
           type: string
+          description: Complaint type.
         sub_type:
           type: string
+          description: Complaint sub-type.
         recipients:
           type: array
           items:
             type: string
+          description: Complained recipients.
       required:
         - inbox_id
         - thread_id
@@ -17354,6 +17895,7 @@ components:
           $ref: '#/components/schemas/type_events:Timestamp'
         reason:
           type: string
+          description: Reject reason.
       required:
         - inbox_id
         - thread_id
@@ -17410,14 +17952,19 @@ components:
       properties:
         type:
           $ref: '#/components/schemas/type_domains:RecordType'
+          description: The type of the DNS record.
         name:
           type: string
+          description: The name or host of the record.
         value:
           type: string
+          description: The value of the record.
         status:
           $ref: '#/components/schemas/type_domains:RecordStatus'
+          description: The verification status of this specific record.
         priority:
           type: integer
+          description: The priority of the MX record.
       required:
         - type
         - name
@@ -17434,20 +17981,24 @@ components:
           $ref: '#/components/schemas/type_domains:DomainId'
         status:
           $ref: '#/components/schemas/type_domains:VerificationStatus'
+          description: The verification status of the domain.
         feedback_enabled:
           $ref: '#/components/schemas/type_domains:FeedbackEnabled'
         records:
           type: array
           items:
             $ref: '#/components/schemas/type_domains:VerificationRecord'
+          description: A list of DNS records required to verify the domain.
         client_id:
           $ref: '#/components/schemas/type_domains:ClientId'
         updated_at:
           type: string
           format: date-time
+          description: Time at which the domain was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which the domain was created.
       required:
         - domain_id
         - status
@@ -17491,10 +18042,12 @@ components:
           type: array
           items:
             type: string
+          description: IDs of the inboxes to subscribe to.
         pod_ids:
           type: array
           items:
             type: string
+          description: IDs of the pods to subscribe to.
       required:
         - type
 
@@ -17586,35 +18139,43 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_metrics:MetricTimestamp'
+          description: Timestamps when messages were sent.
         delivered:
           type: array
           items:
             $ref: '#/components/schemas/type_metrics:MetricTimestamp'
+          description: Timestamps when messages were delivered.
         bounced:
           type: array
           items:
             $ref: '#/components/schemas/type_metrics:MetricTimestamp'
+          description: Timestamps when messages bounced.
         delayed:
           type: array
           items:
             $ref: '#/components/schemas/type_metrics:MetricTimestamp'
+          description: Timestamps when messages were delayed.
         rejected:
           type: array
           items:
             $ref: '#/components/schemas/type_metrics:MetricTimestamp'
+          description: Timestamps when messages were rejected.
         complained:
           type: array
           items:
             $ref: '#/components/schemas/type_metrics:MetricTimestamp'
+          description: Timestamps when messages received complaints.
         received:
           type: array
           items:
             $ref: '#/components/schemas/type_metrics:MetricTimestamp'
+          description: Timestamps when messages were received.
     type_metrics:ListMetricsResponse:
       type: object
       properties:
         message:
           $ref: '#/components/schemas/type_metrics:MessageMetrics'
+          description: Message metrics grouped by event type.
 
 ```
 
@@ -17823,6 +18384,7 @@ components:
         used_at:
           type: string
           format: date-time
+          description: Time at which api key was last used.
         created_at:
           $ref: '#/components/schemas/type_api-keys:CreatedAt'
       required:
@@ -17841,6 +18403,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_api-keys:ApiKey'
+          description: Ordered by `created_at` descending.
       required:
         - count
         - api_keys
@@ -18040,6 +18603,7 @@ components:
           $ref: '#/components/schemas/type_api-keys:ApiKeyId'
         api_key:
           type: string
+          description: API key.
         prefix:
           $ref: '#/components/schemas/type_api-keys:Prefix'
         name:
@@ -18445,9 +19009,11 @@ components:
         updated_at:
           type: string
           format: date-time
+          description: Time at which pod was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which pod was created.
         client_id:
           $ref: '#/components/schemas/type_pods:ClientId'
       required:
@@ -18468,6 +19034,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_pods:Pod'
+          description: Ordered by `created_at` descending.
       required:
         - count
         - pods
@@ -18659,9 +19226,11 @@ components:
         updated_at:
           type: string
           format: date-time
+          description: Time at which pod was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which pod was created.
         client_id:
           $ref: '#/components/schemas/type_pods:ClientId'
       required:
@@ -18867,9 +19436,11 @@ components:
         updated_at:
           type: string
           format: date-time
+          description: Time at which pod was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which pod was created.
         client_id:
           $ref: '#/components/schemas/type_pods:ClientId'
       required:
@@ -19311,9 +19882,11 @@ components:
         updated_at:
           type: string
           format: date-time
+          description: Time at which inbox was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which inbox was created.
       required:
         - pod_id
         - inbox_id
@@ -19332,6 +19905,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_inboxes:Inbox'
+          description: Ordered by `created_at` descending.
       required:
         - count
         - inboxes
@@ -19537,9 +20111,11 @@ components:
         updated_at:
           type: string
           format: date-time
+          description: Time at which inbox was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which inbox was created.
       required:
         - pod_id
         - inbox_id
@@ -19738,8 +20314,12 @@ components:
       properties:
         username:
           type: string
+          description: Username of address. Randomly generated if not specified.
         domain:
           type: string
+          description: >-
+            Domain of address. Must be verified domain. Defaults to
+            `agentmail.to`.
         display_name:
           $ref: '#/components/schemas/type_inboxes:DisplayName'
         client_id:
@@ -19760,9 +20340,11 @@ components:
         updated_at:
           type: string
           format: date-time
+          description: Time at which inbox was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which inbox was created.
       required:
         - pod_id
         - inbox_id
@@ -20327,6 +20909,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_threads:ThreadItem'
+          description: Ordered by `timestamp` descending.
       required:
         - count
         - threads
@@ -20652,6 +21235,9 @@ components:
           type: array
           items:
             type: string
+          description: >-
+            Reply-to addresses. In format `username@domain.com` or `Display Name
+            <username@domain.com>`.
         to:
           $ref: '#/components/schemas/type_messages:MessageTo'
         cc:
@@ -20666,6 +21252,12 @@ components:
           $ref: '#/components/schemas/type_messages:MessageText'
         html:
           $ref: '#/components/schemas/type_messages:MessageHtml'
+        extracted_text:
+          type: string
+          description: Extracted new text content.
+        extracted_html:
+          type: string
+          description: Extracted new HTML content.
         attachments:
           $ref: '#/components/schemas/type_messages:MessageAttachments'
         in_reply_to:
@@ -20728,6 +21320,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_messages:Message'
+          description: Messages in thread. Ordered by `timestamp` ascending.
       required:
         - inbox_id
         - thread_id
@@ -21280,6 +21873,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_drafts:DraftItem'
+          description: Ordered by `updated_at` descending.
       required:
         - count
         - drafts
@@ -21583,6 +22177,7 @@ components:
           type: array
           items:
             type: string
+          description: IDs of previous messages in thread.
         send_status:
           $ref: '#/components/schemas/type_drafts:DraftSendStatus'
         send_at:
@@ -21592,6 +22187,7 @@ components:
         created_at:
           type: string
           format: date-time
+          description: Time at which draft was created.
       required:
         - inbox_id
         - thread_id
@@ -21845,9 +22441,11 @@ components:
         updated_at:
           type: string
           format: date-time
+          description: Time at which the domain was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which the domain was created.
       required:
         - domain_id
         - feedback_enabled
@@ -21866,6 +22464,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_domains:DomainItem'
+          description: Ordered by `created_at` descending.
       required:
         - count
         - domains
@@ -22090,14 +22689,19 @@ components:
       properties:
         type:
           $ref: '#/components/schemas/type_domains:RecordType'
+          description: The type of the DNS record.
         name:
           type: string
+          description: The name or host of the record.
         value:
           type: string
+          description: The value of the record.
         status:
           $ref: '#/components/schemas/type_domains:RecordStatus'
+          description: The verification status of this specific record.
         priority:
           type: integer
+          description: The priority of the MX record.
       required:
         - type
         - name
@@ -22114,20 +22718,24 @@ components:
           $ref: '#/components/schemas/type_domains:DomainId'
         status:
           $ref: '#/components/schemas/type_domains:VerificationStatus'
+          description: The verification status of the domain.
         feedback_enabled:
           $ref: '#/components/schemas/type_domains:FeedbackEnabled'
         records:
           type: array
           items:
             $ref: '#/components/schemas/type_domains:VerificationRecord'
+          description: A list of DNS records required to verify the domain.
         client_id:
           $ref: '#/components/schemas/type_domains:ClientId'
         updated_at:
           type: string
           format: date-time
+          description: Time at which the domain was last updated.
         created_at:
           type: string
           format: date-time
+          description: Time at which the domain was created.
       required:
         - domain_id
         - status