agentmail 0.1.9 → 0.1.12

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:e3f88ce1-e53f-439a-aeac-faf190593e5b" 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.
 
@@ -169,7 +171,7 @@ This guide will walk you through installing the AgentMail SDK, authenticating wi
   <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:b6a2250c-78ed-4c96-ae69-b8601bae53b8) Click
+    dashboard. ![API Key Creation Screenshot](file:2fa577e4-6c00-4f62-ae2b-9ba5079d20cb) 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
@@ -272,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>
@@ -320,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:4479b8d5-647b-428f-9c43-5202aafa5175" alt="AgentMail Organizational Hierarchy" />
+<img src="file:6419a54d-fe30-4f23-b249-ac2842dc7b83" alt="AgentMail Organizational Hierarchy" />
 
 <Steps>
   <Step title="Organization">
@@ -355,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
@@ -740,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:a3eb4249-4892-4a88-b6d3-9bcaa7e79044" alt="rendered css" />
+  <img src="file:10d09a4f-c2d8-4127-899a-025a124b54f1" alt="rendered css" />
 </Frame>
 
 ## Receiving `Messages`
@@ -1143,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`
 
@@ -1166,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"
+  }]
   )
 
   ```
@@ -1215,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)
 
   ```
 
@@ -1979,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:9be82773-96e6-4707-90e4-049e00ecc897" alt="Download BIND Zone File from Console" />
+      <img src="file:bc58b8c2-8e6f-4282-82ae-d5bab90972e4" alt="Download BIND Zone File from Console" />
     </Frame>
 
     <Tabs>
@@ -1990,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:52e201a6-6877-492d-8ceb-d68103640c2d" alt="AWS Route 53 BIND Import" />
+          <img src="file:b13c1ad1-3e9a-4673-992c-fb5ef7d689aa" 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:6afc53aa-83cf-47c5-b751-b2ff42f86fc9" alt="AWS Route 53 BIND Import" />
+          <img src="file:c44a24d3-4c13-4dc0-a0c8-1acbff875faf" alt="AWS Route 53 BIND Import" />
         </Frame>
 
         4. Review the records and click **"Import"**
@@ -2009,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:a5aac2ea-d73e-4931-b5b9-ff49cecc4f1e" alt="Cloudflare BIND Import" />
+          <img src="file:780cb57b-57ac-4019-93e9-56db287eadaa" 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:d92b7899-42d5-4622-8a7c-93c3dfde145d" alt="Cloudflare BIND Import" />
+          <img src="file:ff8604b6-bc3f-4665-b21e-35753a033a93" alt="Cloudflare BIND Import" />
         </Frame>
 
         4. Upload the downloaded BIND zone file as is
@@ -2028,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:dd25616b-848d-43b5-98da-91f256c8c435" alt="Porkbun DNS Management" />
+          <img src="file:e68ed8f1-092a-40cc-971d-adb5bcd868cc" alt="Porkbun DNS Management" />
         </Frame>
 
         3. Scroll down to the quick upload section
 
         <Frame caption="Upload your BIND zone file here">
-          <img src="file:807e2a16-6fe3-4fce-bdf8-cd5333ef8459" alt="Porkbun Zone File Import" />
+          <img src="file:5d596ae8-43ee-4c8a-af62-459f250b7301" alt="Porkbun Zone File Import" />
         </Frame>
 
         4. Upload the downloaded BIND zone file as is
@@ -2118,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:8f29da71-dcd0-42e2-9d1d-ffd6fbc5fa62" alt="AWS Route 53 Record Configuration" />
+              <img src="file:496e2c29-5f47-4ab0-8f86-752e2b9ee25e" alt="AWS Route 53 Record Configuration" />
             </Frame>
 
             * **TXT (DMARC/SPF):**
@@ -2553,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",
@@ -2599,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>
 
-## Future Events
+### `message.sent`
 
-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 message is successfully sent from one of your `Inboxes`.
+* **Use Case:** Track outgoing messages, update your database, or trigger follow-up workflows after sending.
 
-* `delivery.success`
-* `delivery.bounced`
-* `delivery.complained`
-* and much more...
+<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>
 
-Stay tuned for updates as we roll out these new features!
+### `message.delivered`
 
-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)
+* **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.
 
-```
-```
+<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>
+
+<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>
+
+  <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
@@ -2654,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:3be3ba9b-4849-4adb-85b5-b1dd53489224" alt="Ngrok homepage" />
+<img src="file:12e912a8-9a87-4eca-bf52-b8b22ca64196" 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:3606f774-41a5-4e9a-b513-8818ded10a21" alt="Ngrok setup instructions" />
+<img src="file:36deb6da-c444-4272-9156-2afdfe357619" alt="Ngrok setup instructions" />
 
 For macOS, you can install ngrok via Homebrew:
 
@@ -2706,7 +2894,7 @@ ngrok http 3000
 
 You should see output similar to this:
 
-<img src="file:99864be8-6721-4b52-bae1-981cee8bd478" alt="Ngrok terminal output" />
+<img src="file:f0447993-8b76-4dad-af12-a208a27dba82" 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.
 
@@ -2803,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:65bc3605-d0f1-41cc-bd3c-7c6138eed70c" alt="Webhook receiver status page" />
+<img src="file:10c88199-7f82-479b-ab0a-eb727623ef3c" alt="Webhook receiver status page" />
 
 ## Testing Your Setup
 
@@ -2871,189 +3059,564 @@ For production deployments:
 </CardGroup>
 
 
-# Email Deliverability
-
-> Learn the strategies and best practices for maximizing your email deliverability with AgentMail.
+# WebSockets
 
-## What is Email Deliverability?
+> Learn how to use WebSockets for instant email notifications without webhooks or polling.
 
-Email deliverability is the art and science of getting your emails into your recipients' inboxes. It's not just about hitting "send"; it's about building a good reputation with email providers like Gmail and Outlook so they trust that you're sending valuable content, not spam.
+WebSockets provide a persistent, bidirectional connection to AgentMail for receiving email events in real-time. Unlike webhooks, WebSockets don't require a public URL or external tools like ngrok.
 
-High deliverability is the key to successful email automation. This guide will walk you through the best practices for both your sending strategy and your email content.
+## Why Use WebSockets?
 
-### The Technical Foundation: SPF, DKIM, DMARC
+| Feature    | Webhook                     | WebSocket                |
+| ---------- | --------------------------- | ------------------------ |
+| Setup      | Requires public URL + ngrok | No external tools needed |
+| Connection | HTTP request per event      | Persistent connection    |
+| Direction  | AgentMail → Your server     | Bidirectional            |
+| Firewall   | Must expose port            | Outbound only            |
+| Latency    | HTTP round-trip             | Instant streaming        |
 
-Before you send your first email, it's important to have the right technical foundation in place. SPF, DKIM, and DMARC are DNS records that act as a digital signature, proving to email providers that you are who you say you are.
+***
 
-<Tip>
-  We take care of all of this for you guys, so no need to worry about these.
-  Just something to know about(or google).
-</Tip>
+## Python SDK
 
-For maximum control and the best deliverability, we strongly recommend using your own custom domains. Setting these records up correctly on your own domain is the single most important step you can take.
+The Python SDK provides both synchronous and asynchronous WebSocket clients.
 
-<CardGroup>
-  <Card title="Guide: Managing Custom Domains" icon="fa-solid fa-shield-alt" href="/custom-domains">
-    Learn how to add your own domain and configure SPF, DKIM, and DMARC records.
-  </Card>
-</CardGroup>
+### Async Usage
 
-## High-Volume Sending Strategy
+```python
+import asyncio
+from agentmail import AsyncAgentMail, Subscribe, Subscribed, MessageReceivedEvent
 
-How you send your emails is just as important as what you send. If you're sending a large volume of emails, follow these steps to build and maintain a strong sender reputation.
+client = AsyncAgentMail(api_key="YOUR_API_KEY")
 
-<Steps>
-  <Step title="Warm-Up Your Inboxes">
-    Don't go from zero to one thousand emails overnight. Email providers get
-    suspicious of new inboxes that immediately send a high volume. Start slow
-    and gradually increase your sending volume over several days or weeks. This
-    "warm-up" process signals that you're a legitimate sender.
+async def main():
+    async with client.websockets.connect() as socket:
+        # Subscribe to inboxes
+        await socket.send_subscribe(Subscribe(inbox_ids=["agent@agentmail.to"]))
 
-    <Callout intent="info">
-      **Example Warm-Up Schedule:**
-      <br /> - Day 1: 10 emails/inbox
-      <br /> - Day 2: 20 emails/inbox
-      <br /> - Day 3: 40 emails/inbox
-      <br /> - ...and so on.
-    </Callout>
-  </Step>
+        # Process events as they arrive
+        async for event in socket:
+            if isinstance(event, Subscribed):
+                print(f"Subscribed to: {event.inbox_ids}")
+            elif isinstance(event, MessageReceivedEvent):
+                print(f"New email from: {event.message.from_}")
+                print(f"Subject: {event.message.subject}")
 
-  <Step title="Diversify Your Sending Inboxes">
-    Instead of sending 10,000 emails from a single inbox, it's far better to
-    send 100 emails from 100 different inboxes. This distributes your sending
-    volume, reduces the risk of any single inbox getting flagged, and looks much
-    more natural to email providers. AgentMail's ability to create inboxes at
-    scale makes this strategy easy to implement.
+asyncio.run(main())
+```
 
-    <img src="file:9510cd76-587b-4d97-97d8-d8ed463903ee" alt="Diagram comparing one inbox sending 1000 emails vs. five inboxes sending 200 each." />
-  </Step>
+### Sync Usage
 
-  <Step title="Protect Your Reputation with Multiple Domains">
-    An email domain's reputation is its most valuable asset. To protect it, use
-    multiple custom domains for your outreach campaigns. If one domain's
-    reputation is inadvertently damaged, you can cycle it out without impacting
-    the deliverability of your other domains.
-  </Step>
-</Steps>
+```python
+from agentmail import AgentMail, Subscribe, Subscribed, MessageReceivedEvent
 
-## High-Impact Content Strategy
+client = AgentMail(api_key="YOUR_API_KEY")
 
-The content of your email plays a huge role in whether it's seen as a valuable message or as spam.
+with client.websockets.connect() as socket:
+    # Subscribe to inboxes
+    socket.send_subscribe(Subscribe(inbox_ids=["agent@agentmail.to"]))
 
-<Steps>
-  <Step title="Personalize Everything">
-    Address your recipients by name in the subject line and email body. Use
-    other data points you have to make the email feel like a one-to-one
-    conversation, not a mass blast. Generic emails are a major red flag for spam
-    filters.
-  </Step>
+    # Process events as they arrive
+    for event in socket:
+        if isinstance(event, Subscribed):
+            print(f"Subscribed to: {event.inbox_ids}")
+        elif isinstance(event, MessageReceivedEvent):
+            print(f"New email from: {event.message.from_}")
+            print(f"Subject: {event.message.subject}")
+```
 
-  <Step title="Write Like a Human, Not a Marketer">
-    Avoid "spammy" keywords (e.g., "free," "buy now," "limited time offer"),
-    excessive exclamation points, and using all caps. Write in a natural,
-    conversational tone. The goal is to start a conversation, not to close a
-    sale in the first email.
-  </Step>
+### Event Handler Pattern
 
-  <Step title="Be Strategic with images">
-    Any type of image that isn't an attachment but included in the message body
-    actually sets of the spam alarms. Don't do it. Also get rid of your
-    open-tracker while your at it because how EVERY service checks if the
-    reciepeint of your email opened your message is by encoding a small image
-    into the body. Hurts deliverability!!
-  </Step>
+You can also use event handlers instead of iterating:
 
-  <Step title="CTA Selection">
-    Email providers are wary of emails links, especially in the first message of
-    a conversation. A great strategy is to send your initial outreach with no
-    links or images. Wait for the recipient to reply, and *then* send your
-    call-to-action (CTA) link. This behavior is viewed far more favorably, as
-    it's now viewd as a "conversation."
-  </Step>
+```python
+import asyncio
+from agentmail import AsyncAgentMail, Subscribe, EventType
 
-  <Step title="HTML + Text">
-    Email providers oftentimes flag emails that only include HTML as spam.
-    Providing a plain text alternative demonstrates the legitimacy of your
-    message to providers like Gmail and increases the chances of it reaching the
-    recipient's inbox.
-  </Step>
-</Steps>
+client = AsyncAgentMail(api_key="YOUR_API_KEY")
 
+async def main():
+    async with client.websockets.connect() as socket:
+        # Register event handlers
+        socket.on(EventType.OPEN, lambda _: print("Connected"))
+        socket.on(EventType.MESSAGE, lambda msg: print("Received:", msg))
+        socket.on(EventType.CLOSE, lambda _: print("Disconnected"))
+        socket.on(EventType.ERROR, lambda err: print("Error:", err))
 
-# Idempotent Requests
+        # Subscribe and start listening
+        await socket.send_subscribe(Subscribe(inbox_ids=["agent@agentmail.to"]))
+        await socket.start_listening()
 
-> A guide to using the client_id parameter in AgentMail to prevent duplicate resources and safely retry API requests.
+asyncio.run(main())
+```
 
-## What is Idempotency?
+For sync usage with event handlers, run the listener in a background thread:
 
-In the context of an API, idempotency is the concept that making the same API request multiple times produces the same result as making it just once. If an idempotent `POST` request to create a resource is sent five times, it only creates the resource on the first call. The next four calls do nothing but return the result of that first successful call.
+```python
+import threading
+from agentmail import AgentMail, Subscribe, EventType
 
-This is a critical feature for building robust, fault-tolerant systems. Network errors, timeouts, and client-side retries are inevitable. Without idempotency, these events could lead to unwanted duplicate resources, like creating multiple identical inboxes or webhooks.
+client = AgentMail(api_key="YOUR_API_KEY")
 
-## How AgentMail Handles Idempotency
+with client.websockets.connect() as socket:
+    socket.on(EventType.OPEN, lambda _: print("Connected"))
+    socket.on(EventType.MESSAGE, lambda msg: print("Received:", msg))
+    socket.on(EventType.CLOSE, lambda _: print("Disconnected"))
+    socket.on(EventType.ERROR, lambda err: print("Error:", err))
 
-AgentMail supports idempotency for all `create` operations via an optional `client_id` parameter.
+    socket.send_subscribe(Subscribe(inbox_ids=["agent@agentmail.to"]))
 
-When you provide a `client_id` with a `create` request, AgentMail checks if a request with that same `client_id` has already been successfully completed.
+    # Start listening in background thread
+    listener = threading.Thread(target=socket.start_listening, daemon=True)
+    listener.start()
+    listener.join()
+```
 
-* **If it's the first time** we've seen this `client_id`, we process the request as normal, create the resource, and store the resulting resource `id` against your `client_id`.
-* **If we have seen this `client_id` before**, we do *not* re-process the request. Instead, we immediately return a `200 OK` response with the data from the *original*, successfully completed request.
+***
 
-This allows you to safely retry requests without the risk of creating duplicate data.
+## TypeScript SDK
 
-```python
-# The first time this code is run, it creates a new inbox.
-inbox = client.inboxes.create(
-    username="idempotent-test",
-    client_id="user-123-inbox-primary"
-)
-print(f"Created inbox: {inbox.id}")
+The TypeScript SDK provides a WebSocket client with automatic reconnection.
 
-# If you run this exact same code again, it will NOT create a second
-# inbox. It will return the same inbox object from the first call.
-inbox_again = client.inboxes.create(
-    username="idempotent-test",
-    client_id="user-123-inbox-primary"
-)
-print(f"Retrieved same inbox: {inbox_again.id}")
-# The inbox.id will be identical in both calls.
-```
+### Basic Usage
 
-## Best Practices for `client_id`
+```typescript
+import { AgentMailClient, AgentMail } from "agentmail";
 
-To use idempotency effectively, the `client_id` you generate must be unique and deterministic.
+const client = new AgentMailClient({
+  apiKey: process.env.AGENTMAIL_API_KEY,
+});
 
-* **Deterministic:** The same logical resource on your end should always generate the same `client_id`. For example, a `client_id` for a user's primary inbox could be `inbox-for-user-{{USER_ID}}`.
-* **Unique:** Do not reuse a `client_id` for creating different resources. A `client_id` used to create an inbox should not be used to create a webhook.
+async function main() {
+  const socket = await client.websockets.connect();
 
-A common and highly effective pattern is to generate a UUID (like a `UUID v4`) on your client side for a resource you are about to create, save that UUID in your own database, and then use it as the `client_id` in the API call. This gives you a reliable key to use for any retries.
+  // Handle events
+  socket.on("open", () => {
+    console.log("Connected");
 
+    // Subscribe to inboxes after connection is open
+    socket.sendSubscribe({
+      type: "subscribe",
+      inboxIds: ["agent@agentmail.to"],
+    });
+  });
 
-# Example: Event-Driven Agent
+  socket.on("message", (event: AgentMail.Subscribed | AgentMail.MessageReceivedEvent) => {
+    if (event.type === "subscribed") {
+      console.log("Subscribed to:", event.inboxIds);
+    } else if (event.type === "message_received") {
+      console.log("New email from:", event.message.from_);
+      console.log("Subject:", event.message.subject);
+    }
+  });
 
-> A step-by-step guide to building a sophisticated agent that performs proactive outreach and uses webhooks for inbound message processing.
+  socket.on("close", (event) => {
+    console.log("Disconnected:", event.code, event.reason);
+  });
 
-This tutorial walks you through building a sophisticated, dual-mode agent. It will:
+  socket.on("error", (error) => {
+    console.error("Error:", error);
+  });
+}
 
-1. **Proactively monitor** a GitHub repository and send an outreach email when it detects a new "star".
-2. **Reactively process** and reply to incoming emails in real-time using AgentMail Webhooks.
+main();
+```
 
-We will use Flask to create a simple web server and `ngrok` to expose it to the internet so AgentMail can send it events.
+### React/Next.js Usage
 
-## Prerequisites
+Using the SDK with React:
 
-Before you start, make sure you have the following:
+```typescript
+import { useEffect, useState } from "react";
+import { AgentMailClient, AgentMail } from "agentmail";
 
-* Python 3.8+
-* An [AgentMail API Key](https://console.agentmail.to/dashboard/api-keys).
-* An [OpenAI account](https://openai.com/) and API key.
-* An [ngrok account](https://ngrok.com/) and authtoken.
+function useAgentMailWebSocket(apiKey: string, inboxIds: string[]) {
+  const [lastMessage, setLastMessage] = useState<AgentMail.MessageReceivedEvent | null>(null);
+  const [isConnected, setIsConnected] = useState(false);
 
-## Step 1: Project Setup
+  useEffect(() => {
+    const client = new AgentMailClient({ apiKey });
 
-First, let's set up your project directory and install the necessary dependencies.
+    let socket: Awaited<ReturnType<typeof client.websockets.connect>>;
 
-1. **Create a project folder** and navigate into it.
+    async function connect() {
+      socket = await client.websockets.connect();
+
+      socket.on("open", () => {
+        setIsConnected(true);
+        socket.sendSubscribe({
+          type: "subscribe",
+          inboxIds,
+        });
+      });
+
+      socket.on("message", (event) => {
+        if (event.type === "message_received") {
+          setLastMessage(event);
+        }
+      });
+
+      socket.on("close", () => setIsConnected(false));
+    }
+
+    connect();
+    return () => socket?.close();
+  }, [apiKey, inboxIds.join(",")]);
+
+  return { lastMessage, isConnected };
+}
+```
+
+***
+
+## Subscribe Options
+
+When subscribing to events, you can filter by inbox, pod, or event type:
+
+**Python:**
+
+```python
+from agentmail import Subscribe
+
+# Subscribe to specific inboxes
+Subscribe(inbox_ids=["inbox1@agentmail.to", "inbox2@agentmail.to"])
+
+# Subscribe to pods
+Subscribe(pod_ids=["pod-id-1", "pod-id-2"])
+
+# Subscribe to specific event types
+Subscribe(
+    inbox_ids=["agent@agentmail.to"],
+    event_types=["message.received", "message.sent"]
+)
+```
+
+**TypeScript:**
+
+```typescript
+// Subscribe to specific inboxes
+socket.sendSubscribe({
+  type: "subscribe",
+  inboxIds: ["inbox1@agentmail.to", "inbox2@agentmail.to"],
+});
+
+// Subscribe to pods
+socket.sendSubscribe({
+  type: "subscribe",
+  podIds: ["pod-id-1", "pod-id-2"],
+});
+
+// Subscribe to specific event types
+socket.sendSubscribe({
+  type: "subscribe",
+  inboxIds: ["agent@agentmail.to"],
+  eventTypes: ["message.received", "message.sent"],
+});
+```
+
+***
+
+## Event Types
+
+### Connection Events
+
+| Event        | Python       | TypeScript             | Description            |
+| ------------ | ------------ | ---------------------- | ---------------------- |
+| `subscribed` | `Subscribed` | `AgentMail.Subscribed` | Subscription confirmed |
+
+### Message Events
+
+| Event                | Python                   | TypeScript                         | Description          |
+| -------------------- | ------------------------ | ---------------------------------- | -------------------- |
+| `message_received`   | `MessageReceivedEvent`   | `AgentMail.MessageReceivedEvent`   | New email received   |
+| `message_sent`       | `MessageSentEvent`       | `AgentMail.MessageSentEvent`       | Email was sent       |
+| `message_delivered`  | `MessageDeliveredEvent`  | `AgentMail.MessageDeliveredEvent`  | Email was delivered  |
+| `message_bounced`    | `MessageBouncedEvent`    | `AgentMail.MessageBouncedEvent`    | Email bounced        |
+| `message_complained` | `MessageComplainedEvent` | `AgentMail.MessageComplainedEvent` | Email marked as spam |
+| `message_rejected`   | `MessageRejectedEvent`   | `AgentMail.MessageRejectedEvent`   | Email was rejected   |
+
+### Domain Events
+
+| Event             | Python                | TypeScript                      | Description                   |
+| ----------------- | --------------------- | ------------------------------- | ----------------------------- |
+| `domain_verified` | `DomainVerifiedEvent` | `AgentMail.DomainVerifiedEvent` | Domain verification completed |
+
+***
+
+## Message Properties
+
+The `event.message` object contains:
+
+| Python        | TypeScript    | Description                   |
+| ------------- | ------------- | ----------------------------- |
+| `inbox_id`    | `inboxId`     | Inbox that received the email |
+| `message_id`  | `messageId`   | Unique message ID             |
+| `thread_id`   | `threadId`    | Conversation thread ID        |
+| `from_`       | `from_`       | Sender email address          |
+| `to`          | `to`          | Recipients list               |
+| `subject`     | `subject`     | Subject line                  |
+| `text`        | `text`        | Plain text body               |
+| `html`        | `html`        | HTML body (if present)        |
+| `attachments` | `attachments` | List of attachments           |
+
+***
+
+## Error Handling
+
+**Python:**
+
+```python
+from agentmail import AsyncAgentMail, Subscribe, MessageReceivedEvent
+from agentmail.core.api_error import ApiError
+
+client = AsyncAgentMail(api_key="YOUR_API_KEY")
+
+async def main():
+    try:
+        async with client.websockets.connect() as socket:
+            await socket.send_subscribe(Subscribe(inbox_ids=["agent@agentmail.to"]))
+
+            async for event in socket:
+                if isinstance(event, MessageReceivedEvent):
+                    await process_email(event.message)
+
+    except ApiError as e:
+        print(f"API error: {e.status_code} - {e.body}")
+    except Exception as e:
+        print(f"Connection error: {e}")
+```
+
+**TypeScript:**
+
+```typescript
+import { AgentMailClient, AgentMail, AgentMailError } from "agentmail";
+
+const client = new AgentMailClient({
+  apiKey: process.env.AGENTMAIL_API_KEY,
+});
+
+async function main() {
+  try {
+    const socket = await client.websockets.connect();
+
+    socket.on("open", () => {
+      socket.sendSubscribe({
+        type: "subscribe",
+        inboxIds: ["agent@agentmail.to"],
+      });
+    });
+
+    socket.on("message", (event: AgentMail.MessageReceivedEvent) => {
+      if (event.type === "message_received") {
+        processEmail(event.message);
+      }
+    });
+
+    socket.on("error", (error) => {
+      console.error("WebSocket error:", error);
+    });
+
+    socket.on("close", (event) => {
+      console.log("Disconnected:", event.code, event.reason);
+    });
+  } catch (err) {
+    if (err instanceof AgentMailError) {
+      console.error(`API error: ${err.statusCode} - ${err.message}`);
+    } else {
+      console.error("Connection error:", err);
+    }
+  }
+}
+
+main();
+```
+
+***
+
+
+# Email Deliverability
+
+> Learn the strategies and best practices for maximizing your email deliverability with AgentMail.
+
+## What is Email Deliverability?
+
+Email deliverability is the art and science of getting your emails into your recipients' inboxes. It's not just about hitting "send"; it's about building a good reputation with email providers like Gmail and Outlook so they trust that you're sending valuable content, not spam.
+
+High deliverability is the key to successful email automation. This guide will walk you through the best practices for both your sending strategy and your email content.
+
+### The Technical Foundation: SPF, DKIM, DMARC
+
+Before you send your first email, it's important to have the right technical foundation in place. SPF, DKIM, and DMARC are DNS records that act as a digital signature, proving to email providers that you are who you say you are.
+
+<Tip>
+  We take care of all of this for you guys, so no need to worry about these.
+  Just something to know about(or google).
+</Tip>
+
+For maximum control and the best deliverability, we strongly recommend using your own custom domains. Setting these records up correctly on your own domain is the single most important step you can take.
+
+<CardGroup>
+  <Card title="Guide: Managing Custom Domains" icon="fa-solid fa-shield-alt" href="/custom-domains">
+    Learn how to add your own domain and configure SPF, DKIM, and DMARC records.
+  </Card>
+</CardGroup>
+
+## High-Volume Sending Strategy
+
+How you send your emails is just as important as what you send. If you're sending a large volume of emails, follow these steps to build and maintain a strong sender reputation.
+
+<Steps>
+  <Step title="Warm-Up Your Inboxes">
+    Don't go from zero to one thousand emails overnight. Email providers get
+    suspicious of new inboxes that immediately send a high volume. Start slow
+    and gradually increase your sending volume over several days or weeks. This
+    "warm-up" process signals that you're a legitimate sender.
+
+    <Callout intent="info">
+      **Example Warm-Up Schedule:**
+      <br /> - Day 1: 10 emails/inbox
+      <br /> - Day 2: 20 emails/inbox
+      <br /> - Day 3: 40 emails/inbox
+      <br /> - ...and so on.
+    </Callout>
+  </Step>
+
+  <Step title="Diversify Your Sending Inboxes">
+    Instead of sending 10,000 emails from a single inbox, it's far better to
+    send 100 emails from 100 different inboxes. This distributes your sending
+    volume, reduces the risk of any single inbox getting flagged, and looks much
+    more natural to email providers. AgentMail's ability to create inboxes at
+    scale makes this strategy easy to implement.
+
+    <img src="file:3417d8c2-94bc-4f35-aaad-c01abf678422" alt="Diagram comparing one inbox sending 1000 emails vs. five inboxes sending 200 each." />
+  </Step>
+
+  <Step title="Protect Your Reputation with Multiple Domains">
+    An email domain's reputation is its most valuable asset. To protect it, use
+    multiple custom domains for your outreach campaigns. If one domain's
+    reputation is inadvertently damaged, you can cycle it out without impacting
+    the deliverability of your other domains.
+  </Step>
+</Steps>
+
+## High-Impact Content Strategy
+
+The content of your email plays a huge role in whether it's seen as a valuable message or as spam.
+
+<Steps>
+  <Step title="Personalize Everything">
+    Address your recipients by name in the subject line and email body. Use
+    other data points you have to make the email feel like a one-to-one
+    conversation, not a mass blast. Generic emails are a major red flag for spam
+    filters.
+  </Step>
+
+  <Step title="Write Like a Human, Not a Marketer">
+    Avoid "spammy" keywords (e.g., "free," "buy now," "limited time offer"),
+    excessive exclamation points, and using all caps. Write in a natural,
+    conversational tone. The goal is to start a conversation, not to close a
+    sale in the first email.
+  </Step>
+
+  <Step title="Be Strategic with images">
+    Any type of image that isn't an attachment but included in the message body
+    actually sets of the spam alarms. Don't do it. Also get rid of your
+    open-tracker while your at it because how EVERY service checks if the
+    reciepeint of your email opened your message is by encoding a small image
+    into the body. Hurts deliverability!!
+  </Step>
+
+  <Step title="CTA Selection">
+    Email providers are wary of emails links, especially in the first message of
+    a conversation. A great strategy is to send your initial outreach with no
+    links or images. Wait for the recipient to reply, and *then* send your
+    call-to-action (CTA) link. This behavior is viewed far more favorably, as
+    it's now viewd as a "conversation."
+  </Step>
+
+  <Step title="HTML + Text">
+    Email providers oftentimes flag emails that only include HTML as spam.
+    Providing a plain text alternative demonstrates the legitimacy of your
+    message to providers like Gmail and increases the chances of it reaching the
+    recipient's inbox.
+  </Step>
+</Steps>
+
+
+# Idempotent Requests
+
+> A guide to using the client_id parameter in AgentMail to prevent duplicate resources and safely retry API requests.
+
+## What is Idempotency?
+
+In the context of an API, idempotency is the concept that making the same API request multiple times produces the same result as making it just once. If an idempotent `POST` request to create a resource is sent five times, it only creates the resource on the first call. The next four calls do nothing but return the result of that first successful call.
+
+This is a critical feature for building robust, fault-tolerant systems. Network errors, timeouts, and client-side retries are inevitable. Without idempotency, these events could lead to unwanted duplicate resources, like creating multiple identical inboxes or webhooks.
+
+## How AgentMail Handles Idempotency
+
+AgentMail supports idempotency for all `create` operations via an optional `client_id` parameter.
+
+When you provide a `client_id` with a `create` request, AgentMail checks if a request with that same `client_id` has already been successfully completed.
+
+* **If it's the first time** we've seen this `client_id`, we process the request as normal, create the resource, and store the resulting resource `id` against your `client_id`.
+* **If we have seen this `client_id` before**, we do *not* re-process the request. Instead, we immediately return a `200 OK` response with the data from the *original*, successfully completed request.
+
+This allows you to safely retry requests without the risk of creating duplicate data.
+
+```python
+# The first time this code is run, it creates a new inbox.
+inbox = client.inboxes.create(
+    username="idempotent-test",
+    client_id="user-123-inbox-primary"
+)
+print(f"Created inbox: {inbox.id}")
+
+# If you run this exact same code again, it will NOT create a second
+# inbox. It will return the same inbox object from the first call.
+inbox_again = client.inboxes.create(
+    username="idempotent-test",
+    client_id="user-123-inbox-primary"
+)
+print(f"Retrieved same inbox: {inbox_again.id}")
+# The inbox.id will be identical in both calls.
+```
+
+## Best Practices for `client_id`
+
+To use idempotency effectively, the `client_id` you generate must be unique and deterministic.
+
+* **Deterministic:** The same logical resource on your end should always generate the same `client_id`. For example, a `client_id` for a user's primary inbox could be `inbox-for-user-{{USER_ID}}`.
+* **Unique:** Do not reuse a `client_id` for creating different resources. A `client_id` used to create an inbox should not be used to create a webhook.
+
+A common and highly effective pattern is to generate a UUID (like a `UUID v4`) on your client side for a resource you are about to create, save that UUID in your own database, and then use it as the `client_id` in the API call. This gives you a reliable key to use for any retries.
+
+
+# Example: Event-Driven Agent
+
+> A step-by-step guide to building a sophisticated agent that performs proactive outreach and uses webhooks for inbound message processing.
+
+This tutorial walks you through building a sophisticated, dual-mode agent. It will:
+
+1. **Proactively monitor** a GitHub repository and send an outreach email when it detects a new "star".
+2. **Reactively process** and reply to incoming emails in real-time using AgentMail Webhooks.
+
+We will use Flask to create a simple web server and `ngrok` to expose it to the internet so AgentMail can send it events.
+
+## Prerequisites
+
+Before you start, make sure you have the following:
+
+* Python 3.8+
+* An [AgentMail API Key](https://console.agentmail.to/dashboard/api-keys).
+* An [OpenAI account](https://openai.com/) and API key.
+* An [ngrok account](https://ngrok.com/) and authtoken.
+
+## Step 1: Project Setup
+
+First, let's set up your project directory and install the necessary dependencies.
+
+1. **Create a project folder** and navigate into it.
 
 2. **Create a `requirements.txt` file** with the following content:
 
@@ -4944,7 +5507,7 @@ Done
 
 Go to your AgentMail inbox and filter by labels to organize your emails:
 
-<img src="file:36c999f1-b941-45cb-8f04-1b062610ef6c" alt="Test image" />
+<img src="file:a6b17d0b-afdd-4747-a4bb-eec153ba7fbc" alt="Test image" />
 
 **Filter by sentiment:**
 
@@ -5766,7 +6329,137 @@ 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 I achievement and Type II certification progress.
+
+> AgentMail has **achieved SOC 2 Type I compliance** (July 2025) and is currently working toward **Type II certification** (target: Q1 2026).
+
+***
+
+## Current Status
+
+<CardGroup cols={2}>
+  <Card title="Type I Achieved" icon="check-circle">
+    **Completed July 2025** - Controls properly designed and in place
+  </Card>
+
+  <Card title="Type II In Progress" icon="spinner">
+    **Target Q1 2026** - Demonstrating operational effectiveness over time
+  </Card>
+</CardGroup>
+
+### Compliance Timeline
+
+| Phase                          | Period              | Status      |
+| ------------------------------ | ------------------- | ----------- |
+| **Type I Preparation**         | June 2025           | Completed   |
+| **Type I Assessment**          | July 2025           | Completed   |
+| **Type II Observation Period** | Aug 2025 - Dec 2025 | In Progress |
+| **Type II Certification**      | Q1 2026             | Target      |
+
+***
+
+## What is SOC 2?
+
+**SOC 2** is an attestation standard by **AICPA** (The American Institute of Certified Public Accountants) evaluating controls over:
+
+1. **Security** - Protection against unauthorized access, both physical and logical
+2. **Availability** - System accessibility and operational performance as committed
+3. **Processing Integrity** - System processing is complete, valid, accurate, timely, and authorized
+4. **Confidentiality** - Information designated as confidential is protected
+5. **Privacy** - Personal information is collected, used, retained, disclosed, and disposed per privacy commitments
+
+### Report Types
+
+* **Type I**: Verifies that security controls are properly **designed** at a point in time.
+* **Type II**: Validates that controls **operate effectively** over a period (typically 6–12 months).
+
+<Callout intent="success">
+  AgentMail's SOC 2 Type I report confirms that our security infrastructure is properly designed and implemented.
+</Callout>
+
+***
+
+## Security Controls Implemented
+
+The following controls have been audited and verified as part of our SOC 2 Type I compliance:
+
+### Access Control
+
+* Role-based access; **least privilege** enforced
+* **MFA** (Multi-Factor Authentication) for administrative access and sensitive operations
+* Quarterly access reviews and revocation upon role change
+
+### Encryption & Key Management
+
+* **TLS 1.2+** for all service/API communications
+* Data at rest encrypted using industry-standard ciphers
+* Centralized **KMS** (Key Management Service) for key generation, rotation, and revocation
+* **Encrypted point-in-time backups** with 30-day retention
+
+See [Security Overview](https://agentmail.to/security) for more details.
+
+### Email Authentication & Anti-Abuse
+
+* **SPF, DKIM, DMARC** configured across all sending domains
+* Real-time scanning of inbound/outbound messages for malware/phishing
+* IP-based **rate limiting** and behavioral abuse detection
+
+See [Email Protocols](https://docs.agentmail.to/email-protocols) for technical details.
+
+### Monitoring & Incident Response
+
+* Centralized logging and anomaly detection with alerting
+* Documented incident response process: detect → triage → contain → eradicate → recover → post-incident review
+* Responsible disclosure channel for external security researchers
+
+### Resilience, Backup & Recovery
+
+* Daily encrypted backups with **30-day retention**
+* Regular **restore tests** to validate RTO/RPO targets
+* Multi-AZ/high-availability architecture for critical components
+
+***
+
+## SOC 2 Control Mapping
+
+| Control Area         | Implementation                                 | SOC 2 Criteria |
+| -------------------- | ---------------------------------------------- | -------------- |
+| Access Control       | RBAC, MFA, quarterly reviews                   | CC6.1–CC6.7    |
+| Encryption & KMS     | TLS 1.2+, at-rest encryption, key rotation     | CC6.8–CC6.9    |
+| Email Authentication | SPF/DKIM/DMARC, anti-abuse filters             | CC7.1–CC7.4    |
+| Threat Monitoring    | Centralized logs, alerts, malware scanning     | CC7.2–CC7.4    |
+| Backup & Recovery    | Daily backups, 30-day retention, restore tests | CC7.3          |
+| Incident Response    | Runbooks, post-mortems, disclosure program     | CC7.4–CC7.5    |
+| Workforce Security   | Security training, NDAs, background checks     | CC5.3–CC5.4    |
+
+> The above mappings reflect our audited Type I controls and are maintained during the Type II observation period.
+
+***
+
+## Type II Certification Progress
+
+AgentMail is currently in the **Type II observation period** (August 2025 - December 2025), during which an independent auditor is testing and validating that our security controls operate effectively over time.
+
+### What's Being Tested
+
+* **Continuous Operation**: Controls function consistently without gaps
+* **Change Management**: Security maintained through system updates and changes
+* **Evidence Collection**: Logs, tickets, training records, access reviews
+* **Incident Handling**: Real-world response to security events (if any)
+
+### Expected Completion
+
+**Q1 2026** - Full SOC 2 Type II certification report from independent CPA firm
+
+Type II certification provides the highest level of assurance that AgentMail's security controls are not only well-designed but also operate effectively over time.
+
+***
+
+## Accessing SOC 2 Reports
+
+Organizations evaluating AgentMail can [request SOC 2 documentation](mailto:security@agentmail.to).
+
+***
 
 
 # API Welcome
@@ -5878,9 +6571,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
@@ -5899,6 +6594,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_inboxes:Inbox'
+          description: Ordered by `created_at` descending.
       required:
         - count
         - inboxes
@@ -6096,9 +6792,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
@@ -6288,8 +6986,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:
@@ -6312,9 +7014,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
@@ -6535,9 +7239,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
@@ -7096,6 +7802,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_threads:ThreadItem'
+          description: Ordered by `timestamp` descending.
       required:
         - count
         - threads
@@ -7419,6 +8126,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:
@@ -7435,8 +8145,10 @@ components:
           $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:
@@ -7499,6 +8211,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_messages:Message'
+          description: Messages in thread. Ordered by `timestamp` ascending.
       required:
         - inbox_id
         - thread_id
@@ -8250,6 +8963,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_messages:MessageItem'
+          description: Ordered by `timestamp` descending.
       required:
         - count
         - messages
@@ -8532,6 +9246,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:
@@ -8548,8 +9265,10 @@ components:
           $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:
@@ -8586,7 +9305,200 @@ async function main() {
         environment: "https://api.agentmail.to",
         apiKey: "YOUR_TOKEN_HERE",
     });
-    await client.inboxes.messages.get("inbox_id", "message_id");
+    await client.inboxes.messages.get("inbox_id", "message_id");
+}
+main();
+
+```
+
+```python
+from agentmail import AgentMail
+
+client = AgentMail(
+    base_url="https://api.agentmail.to",
+    api_key="YOUR_TOKEN_HERE"
+)
+
+client.inboxes.messages.get(
+    inbox_id="inbox_id",
+    message_id="message_id"
+)
+
+```
+
+```go
+package main
+
+import (
+	"fmt"
+	"net/http"
+	"io"
+)
+
+func main() {
+
+	url := "https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id"
+
+	req, _ := http.NewRequest("GET", url, nil)
+
+	req.Header.Add("Authorization", "Bearer <api_key>")
+
+	res, _ := http.DefaultClient.Do(req)
+
+	defer res.Body.Close()
+	body, _ := io.ReadAll(res.Body)
+
+	fmt.Println(res)
+	fmt.Println(string(body))
+
+}
+```
+
+```ruby
+require 'uri'
+require 'net/http'
+
+url = URI("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id")
+
+http = Net::HTTP.new(url.host, url.port)
+http.use_ssl = true
+
+request = Net::HTTP::Get.new(url)
+request["Authorization"] = 'Bearer <api_key>'
+
+response = http.request(request)
+puts response.read_body
+```
+
+```java
+HttpResponse<String> response = Unirest.get("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id")
+  .header("Authorization", "Bearer <api_key>")
+  .asString();
+```
+
+```php
+<?php
+
+$client = new \GuzzleHttp\Client();
+
+$response = $client->request('GET', 'https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id', [
+  'headers' => [
+    'Authorization' => 'Bearer <api_key>',
+  ],
+]);
+
+echo $response->getBody();
+```
+
+```csharp
+var client = new RestClient("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id");
+var request = new RestRequest(Method.GET);
+request.AddHeader("Authorization", "Bearer <api_key>");
+IRestResponse response = client.Execute(request);
+```
+
+```swift
+import Foundation
+
+let headers = ["Authorization": "Bearer <api_key>"]
+
+let request = NSMutableURLRequest(url: NSURL(string: "https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id")! as URL,
+                                        cachePolicy: .useProtocolCachePolicy,
+                                    timeoutInterval: 10.0)
+request.httpMethod = "GET"
+request.allHTTPHeaderFields = headers
+
+let session = URLSession.shared
+let dataTask = session.dataTask(with: request as URLRequest, completionHandler: { (data, response, error) -> Void in
+  if (error != nil) {
+    print(error as Any)
+  } else {
+    let httpResponse = response as? HTTPURLResponse
+    print(httpResponse)
+  }
+})
+
+dataTask.resume()
+```
+
+# Get Attachment
+
+GET https://api.agentmail.to/v0/inboxes/{inbox_id}/messages/{message_id}/attachments/{attachment_id}
+
+Reference: https://docs.agentmail.to/api-reference/inboxes/messages/get-attachment
+
+## OpenAPI Specification
+
+```yaml
+openapi: 3.1.1
+info:
+  title: Get Attachment
+  version: endpoint_inboxes/messages.getAttachment
+paths:
+  /v0/inboxes/{inbox_id}/messages/{message_id}/attachments/{attachment_id}:
+    get:
+      operationId: get-attachment
+      summary: Get Attachment
+      tags:
+        - - subpackage_inboxes
+          - subpackage_inboxes/messages
+      parameters:
+        - name: inbox_id
+          in: path
+          required: true
+          schema:
+            $ref: '#/components/schemas/type_inboxes:InboxId'
+        - name: message_id
+          in: path
+          required: true
+          schema:
+            $ref: '#/components/schemas/type_messages:MessageId'
+        - name: attachment_id
+          in: path
+          required: true
+          schema:
+            $ref: '#/components/schemas/type_attachments:AttachmentId'
+        - name: Authorization
+          in: header
+          description: >-
+            Bearer authentication of the form `Bearer <token>`, where token is
+            your auth token.
+          required: true
+          schema:
+            type: string
+      responses:
+        '200':
+          description: Response with status 200
+          content:
+            application/octet-stream:
+              schema:
+                type: string
+                format: binary
+        '404':
+          description: Error response with status 404
+          content: {}
+components:
+  schemas:
+    type_inboxes:InboxId:
+      type: string
+    type_messages:MessageId:
+      type: string
+    type_attachments:AttachmentId:
+      type: string
+
+```
+
+## SDK Code Examples
+
+```typescript
+import { AgentMailClient } from "agentmail";
+
+async function main() {
+    const client = new AgentMailClient({
+        environment: "https://api.agentmail.to",
+        apiKey: "YOUR_TOKEN_HERE",
+    });
+    await client.inboxes.messages.getAttachment(":inbox_id", ":message_id", ":attachment_id");
 }
 main();
 
@@ -8600,9 +9512,10 @@ client = AgentMail(
     api_key="YOUR_TOKEN_HERE"
 )
 
-client.inboxes.messages.get(
-    inbox_id="inbox_id",
-    message_id="message_id"
+client.inboxes.messages.get_attachment(
+    inbox_id=":inbox_id",
+    message_id=":message_id",
+    attachment_id=":attachment_id"
 )
 
 ```
@@ -8618,7 +9531,7 @@ import (
 
 func main() {
 
-	url := "https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id"
+	url := "https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/attachments/%3Aattachment_id"
 
 	req, _ := http.NewRequest("GET", url, nil)
 
@@ -8639,7 +9552,7 @@ func main() {
 require 'uri'
 require 'net/http'
 
-url = URI("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id")
+url = URI("https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/attachments/%3Aattachment_id")
 
 http = Net::HTTP.new(url.host, url.port)
 http.use_ssl = true
@@ -8652,7 +9565,7 @@ puts response.read_body
 ```
 
 ```java
-HttpResponse<String> response = Unirest.get("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id")
+HttpResponse<String> response = Unirest.get("https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/attachments/%3Aattachment_id")
   .header("Authorization", "Bearer <api_key>")
   .asString();
 ```
@@ -8662,7 +9575,7 @@ HttpResponse<String> response = Unirest.get("https://api.agentmail.to/v0/inboxes
 
 $client = new \GuzzleHttp\Client();
 
-$response = $client->request('GET', 'https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id', [
+$response = $client->request('GET', 'https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/attachments/%3Aattachment_id', [
   'headers' => [
     'Authorization' => 'Bearer <api_key>',
   ],
@@ -8672,7 +9585,7 @@ echo $response->getBody();
 ```
 
 ```csharp
-var client = new RestClient("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id");
+var client = new RestClient("https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/attachments/%3Aattachment_id");
 var request = new RestRequest(Method.GET);
 request.AddHeader("Authorization", "Bearer <api_key>");
 IRestResponse response = client.Execute(request);
@@ -8683,7 +9596,7 @@ import Foundation
 
 let headers = ["Authorization": "Bearer <api_key>"]
 
-let request = NSMutableURLRequest(url: NSURL(string: "https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id")! as URL,
+let request = NSMutableURLRequest(url: NSURL(string: "https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/attachments/%3Aattachment_id")! as URL,
                                         cachePolicy: .useProtocolCachePolicy,
                                     timeoutInterval: 10.0)
 request.httpMethod = "GET"
@@ -8702,24 +9615,24 @@ let dataTask = session.dataTask(with: request as URLRequest, completionHandler:
 dataTask.resume()
 ```
 
-# Get Attachment
+# Get Raw Message
 
-GET https://api.agentmail.to/v0/inboxes/{inbox_id}/messages/{message_id}/attachments/{attachment_id}
+GET https://api.agentmail.to/v0/inboxes/{inbox_id}/messages/{message_id}/raw
 
-Reference: https://docs.agentmail.to/api-reference/inboxes/messages/get-attachment
+Reference: https://docs.agentmail.to/api-reference/inboxes/messages/get-raw
 
 ## OpenAPI Specification
 
 ```yaml
 openapi: 3.1.1
 info:
-  title: Get Attachment
-  version: endpoint_inboxes/messages.getAttachment
+  title: Get Raw Message
+  version: endpoint_inboxes/messages.getRaw
 paths:
-  /v0/inboxes/{inbox_id}/messages/{message_id}/attachments/{attachment_id}:
+  /v0/inboxes/{inbox_id}/messages/{message_id}/raw:
     get:
-      operationId: get-attachment
-      summary: Get Attachment
+      operationId: get-raw
+      summary: Get Raw Message
       tags:
         - - subpackage_inboxes
           - subpackage_inboxes/messages
@@ -8734,11 +9647,6 @@ paths:
           required: true
           schema:
             $ref: '#/components/schemas/type_messages:MessageId'
-        - name: attachment_id
-          in: path
-          required: true
-          schema:
-            $ref: '#/components/schemas/type_attachments:AttachmentId'
         - name: Authorization
           in: header
           description: >-
@@ -8764,8 +9672,6 @@ components:
       type: string
     type_messages:MessageId:
       type: string
-    type_attachments:AttachmentId:
-      type: string
 
 ```
 
@@ -8779,7 +9685,7 @@ async function main() {
         environment: "https://api.agentmail.to",
         apiKey: "YOUR_TOKEN_HERE",
     });
-    await client.inboxes.messages.getAttachment(":inbox_id", ":message_id", ":attachment_id");
+    await client.inboxes.messages.getRaw(":inbox_id", ":message_id");
 }
 main();
 
@@ -8793,10 +9699,9 @@ client = AgentMail(
     api_key="YOUR_TOKEN_HERE"
 )
 
-client.inboxes.messages.get_attachment(
+client.inboxes.messages.get_raw(
     inbox_id=":inbox_id",
-    message_id=":message_id",
-    attachment_id=":attachment_id"
+    message_id=":message_id"
 )
 
 ```
@@ -8812,7 +9717,7 @@ import (
 
 func main() {
 
-	url := "https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/attachments/%3Aattachment_id"
+	url := "https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/raw"
 
 	req, _ := http.NewRequest("GET", url, nil)
 
@@ -8833,7 +9738,7 @@ func main() {
 require 'uri'
 require 'net/http'
 
-url = URI("https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/attachments/%3Aattachment_id")
+url = URI("https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/raw")
 
 http = Net::HTTP.new(url.host, url.port)
 http.use_ssl = true
@@ -8846,7 +9751,7 @@ puts response.read_body
 ```
 
 ```java
-HttpResponse<String> response = Unirest.get("https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/attachments/%3Aattachment_id")
+HttpResponse<String> response = Unirest.get("https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/raw")
   .header("Authorization", "Bearer <api_key>")
   .asString();
 ```
@@ -8856,7 +9761,7 @@ HttpResponse<String> response = Unirest.get("https://api.agentmail.to/v0/inboxes
 
 $client = new \GuzzleHttp\Client();
 
-$response = $client->request('GET', 'https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/attachments/%3Aattachment_id', [
+$response = $client->request('GET', 'https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/raw', [
   'headers' => [
     'Authorization' => 'Bearer <api_key>',
   ],
@@ -8866,7 +9771,7 @@ echo $response->getBody();
 ```
 
 ```csharp
-var client = new RestClient("https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/attachments/%3Aattachment_id");
+var client = new RestClient("https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/raw");
 var request = new RestRequest(Method.GET);
 request.AddHeader("Authorization", "Bearer <api_key>");
 IRestResponse response = client.Execute(request);
@@ -8877,7 +9782,7 @@ import Foundation
 
 let headers = ["Authorization": "Bearer <api_key>"]
 
-let request = NSMutableURLRequest(url: NSURL(string: "https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/attachments/%3Aattachment_id")! as URL,
+let request = NSMutableURLRequest(url: NSURL(string: "https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/raw")! as URL,
                                         cachePolicy: .useProtocolCachePolicy,
                                     timeoutInterval: 10.0)
 request.httpMethod = "GET"
@@ -8896,24 +9801,25 @@ let dataTask = session.dataTask(with: request as URLRequest, completionHandler:
 dataTask.resume()
 ```
 
-# Get Raw Message
+# Send Message
 
-GET https://api.agentmail.to/v0/inboxes/{inbox_id}/messages/{message_id}/raw
+POST https://api.agentmail.to/v0/inboxes/{inbox_id}/messages/send
+Content-Type: application/json
 
-Reference: https://docs.agentmail.to/api-reference/inboxes/messages/get-raw
+Reference: https://docs.agentmail.to/api-reference/inboxes/messages/send
 
 ## OpenAPI Specification
 
 ```yaml
 openapi: 3.1.1
 info:
-  title: Get Raw Message
-  version: endpoint_inboxes/messages.getRaw
+  title: Send Message
+  version: endpoint_inboxes/messages.send
 paths:
-  /v0/inboxes/{inbox_id}/messages/{message_id}/raw:
-    get:
-      operationId: get-raw
-      summary: Get Raw Message
+  /v0/inboxes/{inbox_id}/messages/send:
+    post:
+      operationId: send
+      summary: Send Message
       tags:
         - - subpackage_inboxes
           - subpackage_inboxes/messages
@@ -8923,11 +9829,6 @@ paths:
           required: true
           schema:
             $ref: '#/components/schemas/type_inboxes:InboxId'
-        - name: message_id
-          in: path
-          required: true
-          schema:
-            $ref: '#/components/schemas/type_messages:MessageId'
         - name: Authorization
           in: header
           description: >-
@@ -8940,19 +9841,113 @@ paths:
         '200':
           description: Response with status 200
           content:
-            application/octet-stream:
+            application/json:
               schema:
-                type: string
-                format: binary
+                $ref: '#/components/schemas/type_messages:SendMessageResponse'
+        '400':
+          description: Error response with status 400
+          content: {}
+        '403':
+          description: Error response with status 403
+          content: {}
         '404':
           description: Error response with status 404
           content: {}
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/type_messages:SendMessageRequest'
 components:
   schemas:
     type_inboxes:InboxId:
       type: string
+    type_messages:MessageLabels:
+      type: array
+      items:
+        type: string
+    type_messages:Addresses:
+      oneOf:
+        - type: string
+        - type: array
+          items:
+            type: string
+    type_messages:SendMessageReplyTo:
+      $ref: '#/components/schemas/type_messages:Addresses'
+    type_messages:SendMessageTo:
+      $ref: '#/components/schemas/type_messages:Addresses'
+    type_messages:SendMessageCc:
+      $ref: '#/components/schemas/type_messages:Addresses'
+    type_messages:SendMessageBcc:
+      $ref: '#/components/schemas/type_messages:Addresses'
+    type_messages:MessageSubject:
+      type: string
+    type_messages:MessageText:
+      type: string
+    type_messages:MessageHtml:
+      type: string
+    type_attachments:AttachmentFilename:
+      type: string
+    type_attachments:AttachmentContentType:
+      type: string
+    type_attachments:AttachmentContent:
+      type: string
+    type_attachments:SendAttachment:
+      type: object
+      properties:
+        filename:
+          $ref: '#/components/schemas/type_attachments:AttachmentFilename'
+        content_type:
+          $ref: '#/components/schemas/type_attachments:AttachmentContentType'
+        content:
+          $ref: '#/components/schemas/type_attachments:AttachmentContent'
+      required:
+        - content
+    type_messages:SendMessageAttachments:
+      type: array
+      items:
+        $ref: '#/components/schemas/type_attachments:SendAttachment'
+    type_messages:SendMessageHeaders:
+      type: object
+      additionalProperties:
+        type: string
+    type_messages:SendMessageRequest:
+      type: object
+      properties:
+        labels:
+          $ref: '#/components/schemas/type_messages:MessageLabels'
+        reply_to:
+          $ref: '#/components/schemas/type_messages:SendMessageReplyTo'
+        to:
+          $ref: '#/components/schemas/type_messages:SendMessageTo'
+        cc:
+          $ref: '#/components/schemas/type_messages:SendMessageCc'
+        bcc:
+          $ref: '#/components/schemas/type_messages:SendMessageBcc'
+        subject:
+          $ref: '#/components/schemas/type_messages:MessageSubject'
+        text:
+          $ref: '#/components/schemas/type_messages:MessageText'
+        html:
+          $ref: '#/components/schemas/type_messages:MessageHtml'
+        attachments:
+          $ref: '#/components/schemas/type_messages:SendMessageAttachments'
+        headers:
+          $ref: '#/components/schemas/type_messages:SendMessageHeaders'
     type_messages:MessageId:
       type: string
+    type_threads:ThreadId:
+      type: string
+    type_messages:SendMessageResponse:
+      type: object
+      properties:
+        message_id:
+          $ref: '#/components/schemas/type_messages:MessageId'
+        thread_id:
+          $ref: '#/components/schemas/type_threads:ThreadId'
+      required:
+        - message_id
+        - thread_id
 
 ```
 
@@ -8966,7 +9961,7 @@ async function main() {
         environment: "https://api.agentmail.to",
         apiKey: "YOUR_TOKEN_HERE",
     });
-    await client.inboxes.messages.getRaw(":inbox_id", ":message_id");
+    await client.inboxes.messages.send("inbox_id", {});
 }
 main();
 
@@ -8980,9 +9975,8 @@ client = AgentMail(
     api_key="YOUR_TOKEN_HERE"
 )
 
-client.inboxes.messages.get_raw(
-    inbox_id=":inbox_id",
-    message_id=":message_id"
+client.inboxes.messages.send(
+    inbox_id="inbox_id"
 )
 
 ```
@@ -8992,17 +9986,21 @@ package main
 
 import (
 	"fmt"
+	"strings"
 	"net/http"
 	"io"
 )
 
 func main() {
 
-	url := "https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/raw"
+	url := "https://api.agentmail.to/v0/inboxes/inbox_id/messages/send"
 
-	req, _ := http.NewRequest("GET", url, nil)
+	payload := strings.NewReader("{}")
+
+	req, _ := http.NewRequest("POST", url, payload)
 
 	req.Header.Add("Authorization", "Bearer <api_key>")
+	req.Header.Add("Content-Type", "application/json")
 
 	res, _ := http.DefaultClient.Do(req)
 
@@ -9019,21 +10017,25 @@ func main() {
 require 'uri'
 require 'net/http'
 
-url = URI("https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/raw")
+url = URI("https://api.agentmail.to/v0/inboxes/inbox_id/messages/send")
 
 http = Net::HTTP.new(url.host, url.port)
 http.use_ssl = true
 
-request = Net::HTTP::Get.new(url)
+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
 ```
 
 ```java
-HttpResponse<String> response = Unirest.get("https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/raw")
+HttpResponse<String> response = Unirest.post("https://api.agentmail.to/v0/inboxes/inbox_id/messages/send")
   .header("Authorization", "Bearer <api_key>")
+  .header("Content-Type", "application/json")
+  .body("{}")
   .asString();
 ```
 
@@ -9042,9 +10044,11 @@ HttpResponse<String> response = Unirest.get("https://api.agentmail.to/v0/inboxes
 
 $client = new \GuzzleHttp\Client();
 
-$response = $client->request('GET', 'https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/raw', [
+$response = $client->request('POST', 'https://api.agentmail.to/v0/inboxes/inbox_id/messages/send', [
+  'body' => '{}',
   'headers' => [
     'Authorization' => 'Bearer <api_key>',
+    'Content-Type' => 'application/json',
   ],
 ]);
 
@@ -9052,22 +10056,31 @@ echo $response->getBody();
 ```
 
 ```csharp
-var client = new RestClient("https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/raw");
-var request = new RestRequest(Method.GET);
+var client = new RestClient("https://api.agentmail.to/v0/inboxes/inbox_id/messages/send");
+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);
 ```
 
 ```swift
 import Foundation
 
-let headers = ["Authorization": "Bearer <api_key>"]
+let headers = [
+  "Authorization": "Bearer <api_key>",
+  "Content-Type": "application/json"
+]
+let parameters = [] as [String : Any]
 
-let request = NSMutableURLRequest(url: NSURL(string: "https://api.agentmail.to/v0/inboxes/%3Ainbox_id/messages/%3Amessage_id/raw")! as URL,
+let postData = JSONSerialization.data(withJSONObject: parameters, options: [])
+
+let request = NSMutableURLRequest(url: NSURL(string: "https://api.agentmail.to/v0/inboxes/inbox_id/messages/send")! as URL,
                                         cachePolicy: .useProtocolCachePolicy,
                                     timeoutInterval: 10.0)
-request.httpMethod = "GET"
+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
@@ -9082,25 +10095,25 @@ let dataTask = session.dataTask(with: request as URLRequest, completionHandler:
 dataTask.resume()
 ```
 
-# Send Message
+# Reply To Message
 
-POST https://api.agentmail.to/v0/inboxes/{inbox_id}/messages/send
+POST https://api.agentmail.to/v0/inboxes/{inbox_id}/messages/{message_id}/reply
 Content-Type: application/json
 
-Reference: https://docs.agentmail.to/api-reference/inboxes/messages/send
+Reference: https://docs.agentmail.to/api-reference/inboxes/messages/reply
 
 ## OpenAPI Specification
 
 ```yaml
 openapi: 3.1.1
 info:
-  title: Send Message
-  version: endpoint_inboxes/messages.send
+  title: Reply To Message
+  version: endpoint_inboxes/messages.reply
 paths:
-  /v0/inboxes/{inbox_id}/messages/send:
-    post:
-      operationId: send
-      summary: Send Message
+  /v0/inboxes/{inbox_id}/messages/{message_id}/reply:
+    post:
+      operationId: reply
+      summary: Reply To Message
       tags:
         - - subpackage_inboxes
           - subpackage_inboxes/messages
@@ -9110,6 +10123,11 @@ paths:
           required: true
           schema:
             $ref: '#/components/schemas/type_inboxes:InboxId'
+        - name: message_id
+          in: path
+          required: true
+          schema:
+            $ref: '#/components/schemas/type_messages:MessageId'
         - name: Authorization
           in: header
           description: >-
@@ -9138,11 +10156,13 @@ paths:
         content:
           application/json:
             schema:
-              $ref: '#/components/schemas/type_messages:SendMessageRequest'
+              $ref: '#/components/schemas/type_messages:ReplyToMessageRequest'
 components:
   schemas:
     type_inboxes:InboxId:
       type: string
+    type_messages:MessageId:
+      type: string
     type_messages:MessageLabels:
       type: array
       items:
@@ -9161,8 +10181,8 @@ components:
       $ref: '#/components/schemas/type_messages:Addresses'
     type_messages:SendMessageBcc:
       $ref: '#/components/schemas/type_messages:Addresses'
-    type_messages:MessageSubject:
-      type: string
+    type_messages:ReplyAll:
+      type: boolean
     type_messages:MessageText:
       type: string
     type_messages:MessageHtml:
@@ -9192,7 +10212,7 @@ components:
       type: object
       additionalProperties:
         type: string
-    type_messages:SendMessageRequest:
+    type_messages:ReplyToMessageRequest:
       type: object
       properties:
         labels:
@@ -9205,8 +10225,8 @@ components:
           $ref: '#/components/schemas/type_messages:SendMessageCc'
         bcc:
           $ref: '#/components/schemas/type_messages:SendMessageBcc'
-        subject:
-          $ref: '#/components/schemas/type_messages:MessageSubject'
+        reply_all:
+          $ref: '#/components/schemas/type_messages:ReplyAll'
         text:
           $ref: '#/components/schemas/type_messages:MessageText'
         html:
@@ -9215,8 +10235,6 @@ components:
           $ref: '#/components/schemas/type_messages:SendMessageAttachments'
         headers:
           $ref: '#/components/schemas/type_messages:SendMessageHeaders'
-    type_messages:MessageId:
-      type: string
     type_threads:ThreadId:
       type: string
     type_messages:SendMessageResponse:
@@ -9242,7 +10260,7 @@ async function main() {
         environment: "https://api.agentmail.to",
         apiKey: "YOUR_TOKEN_HERE",
     });
-    await client.inboxes.messages.send("inbox_id", {});
+    await client.inboxes.messages.reply("inbox_id", "message_id", {});
 }
 main();
 
@@ -9256,8 +10274,9 @@ client = AgentMail(
     api_key="YOUR_TOKEN_HERE"
 )
 
-client.inboxes.messages.send(
-    inbox_id="inbox_id"
+client.inboxes.messages.reply(
+    inbox_id="inbox_id",
+    message_id="message_id"
 )
 
 ```
@@ -9274,7 +10293,7 @@ import (
 
 func main() {
 
-	url := "https://api.agentmail.to/v0/inboxes/inbox_id/messages/send"
+	url := "https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply"
 
 	payload := strings.NewReader("{}")
 
@@ -9298,7 +10317,7 @@ func main() {
 require 'uri'
 require 'net/http'
 
-url = URI("https://api.agentmail.to/v0/inboxes/inbox_id/messages/send")
+url = URI("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply")
 
 http = Net::HTTP.new(url.host, url.port)
 http.use_ssl = true
@@ -9313,7 +10332,7 @@ puts response.read_body
 ```
 
 ```java
-HttpResponse<String> response = Unirest.post("https://api.agentmail.to/v0/inboxes/inbox_id/messages/send")
+HttpResponse<String> response = Unirest.post("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply")
   .header("Authorization", "Bearer <api_key>")
   .header("Content-Type", "application/json")
   .body("{}")
@@ -9325,7 +10344,7 @@ 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/inbox_id/messages/send', [
+$response = $client->request('POST', 'https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply', [
   'body' => '{}',
   'headers' => [
     'Authorization' => 'Bearer <api_key>',
@@ -9337,7 +10356,7 @@ echo $response->getBody();
 ```
 
 ```csharp
-var client = new RestClient("https://api.agentmail.to/v0/inboxes/inbox_id/messages/send");
+var client = new RestClient("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply");
 var request = new RestRequest(Method.POST);
 request.AddHeader("Authorization", "Bearer <api_key>");
 request.AddHeader("Content-Type", "application/json");
@@ -9356,7 +10375,7 @@ let parameters = [] as [String : Any]
 
 let postData = JSONSerialization.data(withJSONObject: parameters, options: [])
 
-let request = NSMutableURLRequest(url: NSURL(string: "https://api.agentmail.to/v0/inboxes/inbox_id/messages/send")! as URL,
+let request = NSMutableURLRequest(url: NSURL(string: "https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply")! as URL,
                                         cachePolicy: .useProtocolCachePolicy,
                                     timeoutInterval: 10.0)
 request.httpMethod = "POST"
@@ -9376,25 +10395,25 @@ let dataTask = session.dataTask(with: request as URLRequest, completionHandler:
 dataTask.resume()
 ```
 
-# Reply To Message
+# Reply All Message
 
-POST https://api.agentmail.to/v0/inboxes/{inbox_id}/messages/{message_id}/reply
+POST https://api.agentmail.to/v0/inboxes/{inbox_id}/messages/{message_id}/reply-all
 Content-Type: application/json
 
-Reference: https://docs.agentmail.to/api-reference/inboxes/messages/reply
+Reference: https://docs.agentmail.to/api-reference/inboxes/messages/reply-all
 
 ## OpenAPI Specification
 
 ```yaml
 openapi: 3.1.1
 info:
-  title: Reply To Message
-  version: endpoint_inboxes/messages.reply
+  title: Reply All Message
+  version: endpoint_inboxes/messages.reply-all
 paths:
-  /v0/inboxes/{inbox_id}/messages/{message_id}/reply:
+  /v0/inboxes/{inbox_id}/messages/{message_id}/reply-all:
     post:
-      operationId: reply
-      summary: Reply To Message
+      operationId: reply-all
+      summary: Reply All Message
       tags:
         - - subpackage_inboxes
           - subpackage_inboxes/messages
@@ -9437,7 +10456,7 @@ paths:
         content:
           application/json:
             schema:
-              $ref: '#/components/schemas/type_messages:ReplyToMessageRequest'
+              $ref: '#/components/schemas/type_messages:ReplyAllMessageRequest'
 components:
   schemas:
     type_inboxes:InboxId:
@@ -9456,12 +10475,6 @@ components:
             type: string
     type_messages:SendMessageReplyTo:
       $ref: '#/components/schemas/type_messages:Addresses'
-    type_messages:SendMessageTo:
-      $ref: '#/components/schemas/type_messages:Addresses'
-    type_messages:SendMessageCc:
-      $ref: '#/components/schemas/type_messages:Addresses'
-    type_messages:SendMessageBcc:
-      $ref: '#/components/schemas/type_messages:Addresses'
     type_messages:MessageText:
       type: string
     type_messages:MessageHtml:
@@ -9491,19 +10504,13 @@ components:
       type: object
       additionalProperties:
         type: string
-    type_messages:ReplyToMessageRequest:
+    type_messages:ReplyAllMessageRequest:
       type: object
       properties:
         labels:
           $ref: '#/components/schemas/type_messages:MessageLabels'
         reply_to:
           $ref: '#/components/schemas/type_messages:SendMessageReplyTo'
-        to:
-          $ref: '#/components/schemas/type_messages:SendMessageTo'
-        cc:
-          $ref: '#/components/schemas/type_messages:SendMessageCc'
-        bcc:
-          $ref: '#/components/schemas/type_messages:SendMessageBcc'
         text:
           $ref: '#/components/schemas/type_messages:MessageText'
         html:
@@ -9537,7 +10544,7 @@ async function main() {
         environment: "https://api.agentmail.to",
         apiKey: "YOUR_TOKEN_HERE",
     });
-    await client.inboxes.messages.reply("inbox_id", "message_id", {});
+    await client.inboxes.messages.replyAll("inbox_id", "message_id", {});
 }
 main();
 
@@ -9551,7 +10558,7 @@ client = AgentMail(
     api_key="YOUR_TOKEN_HERE"
 )
 
-client.inboxes.messages.reply(
+client.inboxes.messages.reply_all(
     inbox_id="inbox_id",
     message_id="message_id"
 )
@@ -9570,7 +10577,7 @@ import (
 
 func main() {
 
-	url := "https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply"
+	url := "https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply-all"
 
 	payload := strings.NewReader("{}")
 
@@ -9594,7 +10601,7 @@ func main() {
 require 'uri'
 require 'net/http'
 
-url = URI("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply")
+url = URI("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply-all")
 
 http = Net::HTTP.new(url.host, url.port)
 http.use_ssl = true
@@ -9609,7 +10616,7 @@ puts response.read_body
 ```
 
 ```java
-HttpResponse<String> response = Unirest.post("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply")
+HttpResponse<String> response = Unirest.post("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply-all")
   .header("Authorization", "Bearer <api_key>")
   .header("Content-Type", "application/json")
   .body("{}")
@@ -9621,7 +10628,7 @@ 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/inbox_id/messages/message_id/reply', [
+$response = $client->request('POST', 'https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply-all', [
   'body' => '{}',
   'headers' => [
     'Authorization' => 'Bearer <api_key>',
@@ -9633,7 +10640,7 @@ echo $response->getBody();
 ```
 
 ```csharp
-var client = new RestClient("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply");
+var client = new RestClient("https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply-all");
 var request = new RestRequest(Method.POST);
 request.AddHeader("Authorization", "Bearer <api_key>");
 request.AddHeader("Content-Type", "application/json");
@@ -9652,7 +10659,7 @@ let parameters = [] as [String : Any]
 
 let postData = JSONSerialization.data(withJSONObject: parameters, options: [])
 
-let request = NSMutableURLRequest(url: NSURL(string: "https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply")! as URL,
+let request = NSMutableURLRequest(url: NSURL(string: "https://api.agentmail.to/v0/inboxes/inbox_id/messages/message_id/reply-all")! as URL,
                                         cachePolicy: .useProtocolCachePolicy,
                                     timeoutInterval: 10.0)
 request.httpMethod = "POST"
@@ -9744,10 +10751,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:
@@ -9843,6 +10852,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:
@@ -9859,8 +10871,10 @@ components:
           $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:
@@ -10244,6 +11258,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_drafts:DraftItem'
+          description: Ordered by `updated_at` descending.
       required:
         - count
         - drafts
@@ -10545,6 +11560,7 @@ components:
           type: array
           items:
             type: string
+          description: IDs of previous messages in thread.
         send_status:
           $ref: '#/components/schemas/type_drafts:DraftSendStatus'
         send_at:
@@ -10554,6 +11570,7 @@ components:
         created_at:
           type: string
           format: date-time
+          description: Time at which draft was created.
       required:
         - inbox_id
         - thread_id
@@ -10886,6 +11903,7 @@ components:
           type: array
           items:
             type: string
+          description: IDs of previous messages in thread.
         send_status:
           $ref: '#/components/schemas/type_drafts:DraftSendStatus'
         send_at:
@@ -10895,6 +11913,7 @@ components:
         created_at:
           type: string
           format: date-time
+          description: Time at which draft was created.
       required:
         - inbox_id
         - thread_id
@@ -11244,6 +12263,7 @@ components:
           type: array
           items:
             type: string
+          description: IDs of previous messages in thread.
         send_status:
           $ref: '#/components/schemas/type_drafts:DraftSendStatus'
         send_at:
@@ -11253,6 +12273,7 @@ components:
         created_at:
           type: string
           format: date-time
+          description: Time at which draft was created.
       required:
         - inbox_id
         - thread_id
@@ -11483,10 +12504,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:
@@ -11927,35 +12950,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.
 
 ```
 
@@ -12313,6 +13344,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_threads:ThreadItem'
+          description: Ordered by `timestamp` descending.
       required:
         - count
         - threads
@@ -12628,6 +13660,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:
@@ -12644,8 +13679,10 @@ components:
           $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:
@@ -12708,6 +13745,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_messages:Message'
+          description: Messages in thread. Ordered by `timestamp` ascending.
       required:
         - inbox_id
         - thread_id
@@ -13242,6 +14280,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_drafts:DraftItem'
+          description: Ordered by `updated_at` descending.
       required:
         - count
         - drafts
@@ -13535,6 +14574,7 @@ components:
           type: array
           items:
             type: string
+          description: IDs of previous messages in thread.
         send_status:
           $ref: '#/components/schemas/type_drafts:DraftSendStatus'
         send_at:
@@ -13544,6 +14584,7 @@ components:
         created_at:
           type: string
           format: date-time
+          description: Time at which draft was created.
       required:
         - inbox_id
         - thread_id
@@ -13755,9 +14796,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
@@ -13776,6 +14819,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_domains:DomainItem'
+          description: Ordered by `created_at` descending.
       required:
         - count
         - domains
@@ -13979,14 +15023,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
@@ -14003,20 +15052,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
@@ -14416,14 +15469,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
@@ -14440,20 +15498,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
@@ -15053,14 +16115,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:
@@ -15083,6 +16149,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_webhooks:Webhook'
+          description: Ordered by `created_at` descending.
       required:
         - count
         - webhooks
@@ -15295,14 +16362,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:
@@ -15538,14 +16609,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:
@@ -16047,6 +17122,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:
@@ -16063,8 +17141,10 @@ components:
           $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:
@@ -16088,6 +17168,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:
@@ -16105,11 +17275,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
 
 ```
 
@@ -16192,6 +17365,7 @@ components:
           type: array
           items:
             type: string
+          description: Sent recipients.
       required:
         - inbox_id
         - thread_id
@@ -16302,6 +17476,7 @@ components:
           type: array
           items:
             type: string
+          description: Delivered recipients.
       required:
         - inbox_id
         - thread_id
@@ -16402,8 +17577,10 @@ components:
       properties:
         address:
           type: string
+          description: Recipient address.
         status:
           type: string
+          description: Recipient status.
       required:
         - address
         - status
@@ -16420,12 +17597,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
@@ -16536,12 +17716,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
@@ -16652,6 +17835,7 @@ components:
           $ref: '#/components/schemas/type_events:Timestamp'
         reason:
           type: string
+          description: Reject reason.
       required:
         - inbox_id
         - thread_id
@@ -16766,14 +17950,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
@@ -16790,20 +17979,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
@@ -16957,10 +18150,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:
@@ -17064,6 +18259,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:
@@ -17080,8 +18278,10 @@ components:
           $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:
@@ -17105,6 +18305,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:
@@ -17122,11 +18412,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
@@ -17145,6 +18438,7 @@ components:
           type: array
           items:
             type: string
+          description: Sent recipients.
       required:
         - inbox_id
         - thread_id
@@ -17188,6 +18482,7 @@ components:
           type: array
           items:
             type: string
+          description: Delivered recipients.
       required:
         - inbox_id
         - thread_id
@@ -17221,8 +18516,10 @@ components:
       properties:
         address:
           type: string
+          description: Recipient address.
         status:
           type: string
+          description: Recipient status.
       required:
         - address
         - status
@@ -17239,12 +18536,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
@@ -17288,12 +18588,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
@@ -17337,6 +18640,7 @@ components:
           $ref: '#/components/schemas/type_events:Timestamp'
         reason:
           type: string
+          description: Reject reason.
       required:
         - inbox_id
         - thread_id
@@ -17393,14 +18697,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
@@ -17417,20 +18726,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
@@ -17474,10 +18787,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
 
@@ -17569,35 +18884,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.
 
 ```
 
@@ -17806,6 +19129,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:
@@ -17824,6 +19148,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_api-keys:ApiKey'
+          description: Ordered by `created_at` descending.
       required:
         - count
         - api_keys
@@ -18023,6 +19348,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:
@@ -18428,9 +19754,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:
@@ -18451,6 +19779,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_pods:Pod'
+          description: Ordered by `created_at` descending.
       required:
         - count
         - pods
@@ -18642,9 +19971,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:
@@ -18850,9 +20181,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:
@@ -19294,9 +20627,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
@@ -19315,6 +20650,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_inboxes:Inbox'
+          description: Ordered by `created_at` descending.
       required:
         - count
         - inboxes
@@ -19520,9 +20856,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
@@ -19721,8 +21059,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:
@@ -19743,9 +21085,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
@@ -20310,6 +21654,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_threads:ThreadItem'
+          description: Ordered by `timestamp` descending.
       required:
         - count
         - threads
@@ -20635,6 +21980,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:
@@ -20651,8 +21999,10 @@ components:
           $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:
@@ -20715,6 +22065,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_messages:Message'
+          description: Messages in thread. Ordered by `timestamp` ascending.
       required:
         - inbox_id
         - thread_id
@@ -21267,6 +22618,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_drafts:DraftItem'
+          description: Ordered by `updated_at` descending.
       required:
         - count
         - drafts
@@ -21570,6 +22922,7 @@ components:
           type: array
           items:
             type: string
+          description: IDs of previous messages in thread.
         send_status:
           $ref: '#/components/schemas/type_drafts:DraftSendStatus'
         send_at:
@@ -21579,6 +22932,7 @@ components:
         created_at:
           type: string
           format: date-time
+          description: Time at which draft was created.
       required:
         - inbox_id
         - thread_id
@@ -21832,9 +23186,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
@@ -21853,6 +23209,7 @@ components:
           type: array
           items:
             $ref: '#/components/schemas/type_domains:DomainItem'
+          description: Ordered by `created_at` descending.
       required:
         - count
         - domains
@@ -22077,14 +23434,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
@@ -22101,20 +23463,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