agentmail 0.5.49 → 0.5.51

package/reference.md

@@ -358,6 +358,8 @@ await client.inboxes.update("inbox_id", {});
 <dl>
 <dd>
 
+Deletion is asynchronous. A `202` means it has started. While it runs, requests for this inbox return `409` `resource_deleting`. Poll `GET /v0/inboxes/{inbox_id}` until it returns `404`, then the address is free. If the inbox still has its own API keys, delete returns `409` `cannot_delete`: revoke those keys first.
+
 **CLI:**
 ```bash
 agentmail inboxes delete --inbox-id <inbox_id>
@@ -376,7 +378,7 @@ agentmail inboxes delete --inbox-id <inbox_id>
 <dd>
 
 ```typescript
-await client.inboxes.delete("inbox_id");
+await client.inboxes.delete("my-agent@agentmail.to");
 
 ```
 </dd>
@@ -3180,8 +3182,8 @@ await client.drafts.getAttachment("draft_id", "attachment_id");
 </dl>
 </details>
 
-## Inboxes Accounts
-<details><summary><code>client.inboxes.accounts.<a href="/src/api/resources/inboxes/resources/accounts/client/Client.ts">list</a>(inbox_id, { ...params }) -> AgentMail.ListAccountsResponse</code></summary>
+## Forwarding
+<details><summary><code>client.forwarding.<a href="/src/api/resources/forwarding/client/Client.ts">get</a>() -> AgentMail.Forwarding</code></summary>
 <dl>
 <dd>
 
@@ -3193,7 +3195,13 @@ await client.drafts.getAttachment("draft_id", "attachment_id");
 <dl>
 <dd>
 
-Lists accounts held by the inbox, across all apps. Requires `inbox_read`.
+Get the forwarding the organization sets. Pods and inboxes that set no forwarding of their own
+use this list. Needs an organization-scoped API key.
+
+**CLI:**
+```bash
+agentmail forwarding get
+```
 </dd>
 </dl>
 </dd>
@@ -3208,7 +3216,7 @@ Lists accounts held by the inbox, across all apps. Requires `inbox_read`.
 <dd>
 
 ```typescript
-await client.inboxes.accounts.list("inbox_id");
+await client.forwarding.get();
 
 ```
 </dd>
@@ -3224,23 +3232,7 @@ await client.inboxes.accounts.list("inbox_id");
 <dl>
 <dd>
 
-**inbox_id:** `AgentMail.InboxId` 
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**request:** `AgentMail.inboxes.ListAccountsRequest` 
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**requestOptions:** `AccountsClient.RequestOptions` 
+**requestOptions:** `ForwardingClient.RequestOptions` 
     
 </dd>
 </dl>
@@ -3252,7 +3244,7 @@ await client.inboxes.accounts.list("inbox_id");
 </dl>
 </details>
 
-<details><summary><code>client.inboxes.accounts.<a href="/src/api/resources/inboxes/resources/accounts/client/Client.ts">get</a>(inbox_id, account_id) -> AgentMail.Account</code></summary>
+<details><summary><code>client.forwarding.<a href="/src/api/resources/forwarding/client/Client.ts">update</a>({ ...params }) -> AgentMail.UpdateForwardingResponse</code></summary>
 <dl>
 <dd>
 
@@ -3264,8 +3256,14 @@ await client.inboxes.accounts.list("inbox_id");
 <dl>
 <dd>
 
-Returns one account held by the inbox. An account elsewhere is a 404. Requires
-`inbox_read`.
+Set the addresses the organization forwards to. The list replaces the current one. An address
+that is not verified is saved but receives nothing until it is verified. Needs an
+organization-scoped API key in an organization that has completed agent verification.
+
+**CLI:**
+```bash
+agentmail forwarding update --destinations ops@example.com --destinations archive@example.com
+```
 </dd>
 </dl>
 </dd>
@@ -3280,7 +3278,9 @@ Returns one account held by the inbox. An account elsewhere is a 404. Requires
 <dd>
 
 ```typescript
-await client.inboxes.accounts.get("inbox_id", "d5e9c84f-c2b2-4bf4-b4b0-7ffd7a9ffc32");
+await client.forwarding.update({
+    destinations: ["destinations", "destinations"]
+});
 
 ```
 </dd>
@@ -3296,15 +3296,7 @@ await client.inboxes.accounts.get("inbox_id", "d5e9c84f-c2b2-4bf4-b4b0-7ffd7a9ff
 <dl>
 <dd>
 
-**inbox_id:** `AgentMail.InboxId` 
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**account_id:** `AgentMail.AccountId` 
+**request:** `AgentMail.UpdateForwardingRequest` 
     
 </dd>
 </dl>
@@ -3312,7 +3304,7 @@ await client.inboxes.accounts.get("inbox_id", "d5e9c84f-c2b2-4bf4-b4b0-7ffd7a9ff
 <dl>
 <dd>
 
-**requestOptions:** `AccountsClient.RequestOptions` 
+**requestOptions:** `ForwardingClient.RequestOptions` 
     
 </dd>
 </dl>
@@ -3324,8 +3316,7 @@ await client.inboxes.accounts.get("inbox_id", "d5e9c84f-c2b2-4bf4-b4b0-7ffd7a9ff
 </dl>
 </details>
 
-## Inboxes ApiKeys
-<details><summary><code>client.inboxes.apiKeys.<a href="/src/api/resources/inboxes/resources/apiKeys/client/Client.ts">list</a>(inbox_id, { ...params }) -> AgentMail.ListApiKeysResponse</code></summary>
+<details><summary><code>client.forwarding.<a href="/src/api/resources/forwarding/client/Client.ts">delete</a>() -> AgentMail.Forwarding</code></summary>
 <dl>
 <dd>
 
@@ -3337,9 +3328,13 @@ await client.inboxes.accounts.get("inbox_id", "d5e9c84f-c2b2-4bf4-b4b0-7ffd7a9ff
 <dl>
 <dd>
 
+Remove the organization's forwarding, so its inboxes stop forwarding unless their pod or the
+inbox sets its own. Verified addresses stay verified, so adding one again needs no new code.
+Returns `not_found` when the organization sets no forwarding.
+
 **CLI:**
 ```bash
-agentmail inboxes api-keys list --inbox-id <inbox_id>
+agentmail forwarding delete
 ```
 </dd>
 </dl>
@@ -3355,7 +3350,7 @@ agentmail inboxes api-keys list --inbox-id <inbox_id>
 <dd>
 
 ```typescript
-await client.inboxes.apiKeys.list("inbox_id");
+await client.forwarding.delete();
 
 ```
 </dd>
@@ -3371,23 +3366,7 @@ await client.inboxes.apiKeys.list("inbox_id");
 <dl>
 <dd>
 
-**inbox_id:** `AgentMail.InboxId` 
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**request:** `AgentMail.inboxes.ListApiKeysRequest` 
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**requestOptions:** `ApiKeysClient.RequestOptions` 
+**requestOptions:** `ForwardingClient.RequestOptions` 
     
 </dd>
 </dl>
@@ -3399,7 +3378,7 @@ await client.inboxes.apiKeys.list("inbox_id");
 </dl>
 </details>
 
-<details><summary><code>client.inboxes.apiKeys.<a href="/src/api/resources/inboxes/resources/apiKeys/client/Client.ts">create</a>(inbox_id, { ...params }) -> AgentMail.CreateApiKeyResult</code></summary>
+<details><summary><code>client.forwarding.<a href="/src/api/resources/forwarding/client/Client.ts">startVerification</a>({ ...params }) -> AgentMail.ForwardingVerificationStarted</code></summary>
 <dl>
 <dd>
 
@@ -3411,9 +3390,15 @@ await client.inboxes.apiKeys.list("inbox_id");
 <dl>
 <dd>
 
+Email a confirmation code to an address, so it can receive forwarded mail once confirmed.
+Verification belongs to the organization: once verified, the address can be used at the
+organization, any pod and any inbox. Starting again replaces any code already sent to the
+address. Needs an organization- or pod-scoped API key in an organization that has completed
+agent verification.
+
 **CLI:**
 ```bash
-agentmail inboxes api-keys create --inbox-id <inbox_id> --name "My Key"
+agentmail forwarding start-verification --destination ops@example.com
 ```
 </dd>
 </dl>
@@ -3429,7 +3414,9 @@ agentmail inboxes api-keys create --inbox-id <inbox_id> --name "My Key"
 <dd>
 
 ```typescript
-await client.inboxes.apiKeys.create("inbox_id", {});
+await client.forwarding.startVerification({
+    destination: "destination"
+});
 
 ```
 </dd>
@@ -3445,15 +3432,7 @@ await client.inboxes.apiKeys.create("inbox_id", {});
 <dl>
 <dd>
 
-**inbox_id:** `AgentMail.InboxId` 
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**request:** `AgentMail.CreateApiKeyRequest` 
+**request:** `AgentMail.StartForwardingVerificationRequest` 
     
 </dd>
 </dl>
@@ -3461,7 +3440,7 @@ await client.inboxes.apiKeys.create("inbox_id", {});
 <dl>
 <dd>
 
-**requestOptions:** `ApiKeysClient.RequestOptions` 
+**requestOptions:** `ForwardingClient.RequestOptions` 
     
 </dd>
 </dl>
@@ -3473,7 +3452,7 @@ await client.inboxes.apiKeys.create("inbox_id", {});
 </dl>
 </details>
 
-<details><summary><code>client.inboxes.apiKeys.<a href="/src/api/resources/inboxes/resources/apiKeys/client/Client.ts">update</a>(inbox_id, api_key_id, { ...params }) -> AgentMail.ApiKey</code></summary>
+<details><summary><code>client.forwarding.<a href="/src/api/resources/forwarding/client/Client.ts">confirmVerification</a>({ ...params }) -> AgentMail.ForwardingVerificationConfirmed</code></summary>
 <dl>
 <dd>
 
@@ -3485,9 +3464,14 @@ await client.inboxes.apiKeys.create("inbox_id", {});
 <dl>
 <dd>
 
+Submit the code emailed by Start Verification to verify the address. A code allows 10 wrong
+attempts, then stops working even with the right code, and Start Verification sends a new one.
+Needs an organization- or pod-scoped API key in an organization that has completed agent
+verification.
+
 **CLI:**
 ```bash
-agentmail inboxes api-keys update --inbox-id <inbox_id> --api-key-id <api_key_id> --name "Renamed"
+agentmail forwarding confirm-verification --destination ops@example.com --code 7KQ2M-XW9PD
 ```
 </dd>
 </dl>
@@ -3503,7 +3487,10 @@ agentmail inboxes api-keys update --inbox-id <inbox_id> --api-key-id <api_key_id
 <dd>
 
 ```typescript
-await client.inboxes.apiKeys.update("inbox_id", "api_key_id", {});
+await client.forwarding.confirmVerification({
+    destination: "destination",
+    code: "code"
+});
 
 ```
 </dd>
@@ -3519,23 +3506,7 @@ await client.inboxes.apiKeys.update("inbox_id", "api_key_id", {});
 <dl>
 <dd>
 
-**inbox_id:** `AgentMail.InboxId` 
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**api_key_id:** `AgentMail.ApiKeyId` 
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**request:** `AgentMail.UpdateApiKeyRequest` 
+**request:** `AgentMail.ConfirmForwardingVerificationRequest` 
     
 </dd>
 </dl>
@@ -3543,7 +3514,7 @@ await client.inboxes.apiKeys.update("inbox_id", "api_key_id", {});
 <dl>
 <dd>
 
-**requestOptions:** `ApiKeysClient.RequestOptions` 
+**requestOptions:** `ForwardingClient.RequestOptions` 
     
 </dd>
 </dl>
@@ -3555,7 +3526,8 @@ await client.inboxes.apiKeys.update("inbox_id", "api_key_id", {});
 </dl>
 </details>
 
-<details><summary><code>client.inboxes.apiKeys.<a href="/src/api/resources/inboxes/resources/apiKeys/client/Client.ts">delete</a>(inbox_id, api_key_id) -> void</code></summary>
+## Inboxes Accounts
+<details><summary><code>client.inboxes.accounts.<a href="/src/api/resources/inboxes/resources/accounts/client/Client.ts">list</a>(inbox_id, { ...params }) -> AgentMail.ListAccountsResponse</code></summary>
 <dl>
 <dd>
 
@@ -3567,10 +3539,7 @@ await client.inboxes.apiKeys.update("inbox_id", "api_key_id", {});
 <dl>
 <dd>
 
-**CLI:**
-```bash
-agentmail inboxes api-keys delete --inbox-id <inbox_id> --api-key-id <api_key_id>
-```
+Lists accounts held by the inbox, across all apps. Requires `inbox_read`.
 </dd>
 </dl>
 </dd>
@@ -3585,7 +3554,7 @@ agentmail inboxes api-keys delete --inbox-id <inbox_id> --api-key-id <api_key_id
 <dd>
 
 ```typescript
-await client.inboxes.apiKeys.delete("inbox_id", "api_key_id");
+await client.inboxes.accounts.list("inbox_id");
 
 ```
 </dd>
@@ -3609,7 +3578,7 @@ await client.inboxes.apiKeys.delete("inbox_id", "api_key_id");
 <dl>
 <dd>
 
-**api_key_id:** `AgentMail.ApiKeyId` 
+**request:** `AgentMail.inboxes.ListAccountsRequest` 
     
 </dd>
 </dl>
@@ -3617,7 +3586,7 @@ await client.inboxes.apiKeys.delete("inbox_id", "api_key_id");
 <dl>
 <dd>
 
-**requestOptions:** `ApiKeysClient.RequestOptions` 
+**requestOptions:** `AccountsClient.RequestOptions` 
     
 </dd>
 </dl>
@@ -3629,8 +3598,7 @@ await client.inboxes.apiKeys.delete("inbox_id", "api_key_id");
 </dl>
 </details>
 
-## Inboxes Calendar
-<details><summary><code>client.inboxes.calendar.<a href="/src/api/resources/inboxes/resources/calendar/client/Client.ts">get</a>(inbox_id, { ...params }) -> AgentMail.Calendar</code></summary>
+<details><summary><code>client.inboxes.accounts.<a href="/src/api/resources/inboxes/resources/accounts/client/Client.ts">get</a>(inbox_id, account_id) -> AgentMail.Account</code></summary>
 <dl>
 <dd>
 
@@ -3642,12 +3610,8 @@ await client.inboxes.apiKeys.delete("inbox_id", "api_key_id");
 <dl>
 <dd>
 
-Gets the inbox's calendar. Every inbox has one calendar, so this works before any event is
-created. Its `etag` (also the `ETag` response header) is the value to send in `If-Match` to
-make an update conditional.
-
-Requires the `calendar_read` permission. Calendar is available in US production
-(`api.agentmail.to`) but not yet in EU production (`api.agentmail.eu`), which returns `403`.
+Returns one account held by the inbox. An account elsewhere is a 404. Requires
+`inbox_read`.
 </dd>
 </dl>
 </dd>
@@ -3662,7 +3626,7 @@ Requires the `calendar_read` permission. Calendar is available in US production
 <dd>
 
 ```typescript
-await client.inboxes.calendar.get("scheduler@agentmail.to");
+await client.inboxes.accounts.get("inbox_id", "d5e9c84f-c2b2-4bf4-b4b0-7ffd7a9ffc32");
 
 ```
 </dd>
@@ -3686,7 +3650,7 @@ await client.inboxes.calendar.get("scheduler@agentmail.to");
 <dl>
 <dd>
 
-**request:** `AgentMail.inboxes.GetCalendarRequest` 
+**account_id:** `AgentMail.AccountId` 
     
 </dd>
 </dl>
@@ -3694,7 +3658,7 @@ await client.inboxes.calendar.get("scheduler@agentmail.to");
 <dl>
 <dd>
 
-**requestOptions:** `CalendarClient.RequestOptions` 
+**requestOptions:** `AccountsClient.RequestOptions` 
     
 </dd>
 </dl>
@@ -3706,7 +3670,8 @@ await client.inboxes.calendar.get("scheduler@agentmail.to");
 </dl>
 </details>
 
-<details><summary><code>client.inboxes.calendar.<a href="/src/api/resources/inboxes/resources/calendar/client/Client.ts">update</a>(inbox_id, { ...params }) -> AgentMail.Calendar</code></summary>
+## Inboxes ApiKeys
+<details><summary><code>client.inboxes.apiKeys.<a href="/src/api/resources/inboxes/resources/apiKeys/client/Client.ts">list</a>(inbox_id, { ...params }) -> AgentMail.ListApiKeysResponse</code></summary>
 <dl>
 <dd>
 
@@ -3718,15 +3683,10 @@ await client.inboxes.calendar.get("scheduler@agentmail.to");
 <dl>
 <dd>
 
-Updates the calendar's default time zone. Existing events keep their own `timezone`; only
-events created later without a `timezone` use the new default.
-
-Requires the `calendar_update` permission. To make the update conditional, send the
-calendar's current `etag` in `If-Match`: a stale value returns `412`. Without `If-Match` the
-update applies to the calendar as it is.
-
-Calendar is available in US production (`api.agentmail.to`) but not yet in EU production
-(`api.agentmail.eu`), which returns `403`.
+**CLI:**
+```bash
+agentmail inboxes api-keys list --inbox-id <inbox_id>
+```
 </dd>
 </dl>
 </dd>
@@ -3741,9 +3701,7 @@ Calendar is available in US production (`api.agentmail.to`) but not yet in EU pr
 <dd>
 
 ```typescript
-await client.inboxes.calendar.update("scheduler@agentmail.to", {
-    timezone: "America/New_York"
-});
+await client.inboxes.apiKeys.list("inbox_id");
 
 ```
 </dd>
@@ -3767,7 +3725,7 @@ await client.inboxes.calendar.update("scheduler@agentmail.to", {
 <dl>
 <dd>
 
-**request:** `AgentMail.inboxes.UpdateCalendarRequestWrapper` 
+**request:** `AgentMail.inboxes.ListApiKeysRequest` 
     
 </dd>
 </dl>
@@ -3775,7 +3733,7 @@ await client.inboxes.calendar.update("scheduler@agentmail.to", {
 <dl>
 <dd>
 
-**requestOptions:** `CalendarClient.RequestOptions` 
+**requestOptions:** `ApiKeysClient.RequestOptions` 
     
 </dd>
 </dl>
@@ -3787,7 +3745,7 @@ await client.inboxes.calendar.update("scheduler@agentmail.to", {
 </dl>
 </details>
 
-<details><summary><code>client.inboxes.calendar.<a href="/src/api/resources/inboxes/resources/calendar/client/Client.ts">listEvents</a>(inbox_id, { ...params }) -> AgentMail.ListCalendarEventsResponse</code></summary>
+<details><summary><code>client.inboxes.apiKeys.<a href="/src/api/resources/inboxes/resources/apiKeys/client/Client.ts">create</a>(inbox_id, { ...params }) -> AgentMail.CreateApiKeyResult</code></summary>
 <dl>
 <dd>
 
@@ -3799,17 +3757,10 @@ await client.inboxes.calendar.update("scheduler@agentmail.to", {
 <dl>
 <dd>
 
-Lists the events stored on the calendar: one item per one-off or recurring event, plus one
-item for each edited date of a recurring event (as that dated event, with
-`is_exception: true`). Ordered by most recently updated, and cancelled events are included.
-Use it to sync or manage what you created. To see what is on the calendar in a time window,
-use Get Agenda.
-
-The list is always read in the region that serves the request, so it can trail a change made
-moments earlier by a few seconds. Requires the `calendar_event_read` permission.
-
-Calendar is available in US production (`api.agentmail.to`) but not yet in EU production
-(`api.agentmail.eu`), which returns `403`.
+**CLI:**
+```bash
+agentmail inboxes api-keys create --inbox-id <inbox_id> --name "My Key"
+```
 </dd>
 </dl>
 </dd>
@@ -3824,9 +3775,7 @@ Calendar is available in US production (`api.agentmail.to`) but not yet in EU pr
 <dd>
 
 ```typescript
-await client.inboxes.calendar.listEvents("scheduler@agentmail.to", {
-    limit: 50
-});
+await client.inboxes.apiKeys.create("inbox_id", {});
 
 ```
 </dd>
@@ -3850,7 +3799,7 @@ await client.inboxes.calendar.listEvents("scheduler@agentmail.to", {
 <dl>
 <dd>
 
-**request:** `AgentMail.inboxes.ListCalendarEventsRequest` 
+**request:** `AgentMail.CreateApiKeyRequest` 
     
 </dd>
 </dl>
@@ -3858,7 +3807,7 @@ await client.inboxes.calendar.listEvents("scheduler@agentmail.to", {
 <dl>
 <dd>
 
-**requestOptions:** `CalendarClient.RequestOptions` 
+**requestOptions:** `ApiKeysClient.RequestOptions` 
     
 </dd>
 </dl>
@@ -3870,7 +3819,7 @@ await client.inboxes.calendar.listEvents("scheduler@agentmail.to", {
 </dl>
 </details>
 
-<details><summary><code>client.inboxes.calendar.<a href="/src/api/resources/inboxes/resources/calendar/client/Client.ts">getAgenda</a>(inbox_id, { ...params }) -> AgentMail.ListCalendarEventsResponse</code></summary>
+<details><summary><code>client.inboxes.apiKeys.<a href="/src/api/resources/inboxes/resources/apiKeys/client/Client.ts">update</a>(inbox_id, api_key_id, { ...params }) -> AgentMail.ApiKey</code></summary>
 <dl>
 <dd>
 
@@ -3882,25 +3831,10 @@ await client.inboxes.calendar.listEvents("scheduler@agentmail.to", {
 <dl>
 <dd>
 
-Lists every date on the calendar in a time window, ordered by start time: one-off events,
-and recurring events expanded into their individual dates, with cancelled dates left out.
-Use it to answer "what is on the calendar".
-
-The window defaults to now through 90 days from now and can be at most 366 days. Items omit
-`description`, `metadata` and `attendees`; get an event by ID for the full object. An item
-the inbox is invited to still carries `response_status`, so `needs_action` marks an
-invitation waiting for a reply. Dates of
-recurring events appear only up to about 90 days from now; use List Event Instances for a
-recurring event's later dates. While a recurring event's dates are being regenerated after a
-schedule change, which takes a few seconds, the agenda can briefly leave out some of them;
-dates that have already started or ended stay as they ran.
-
-The agenda is read in the region that serves the request, so it can trail a change made
-moments earlier by a few seconds. Pass `consistency=primary` to read your own change right
-away. Requires the `calendar_event_read` permission.
-
-Calendar is available in US production (`api.agentmail.to`) but not yet in EU production
-(`api.agentmail.eu`), which returns `403`.
+**CLI:**
+```bash
+agentmail inboxes api-keys update --inbox-id <inbox_id> --api-key-id <api_key_id> --name "Renamed"
+```
 </dd>
 </dl>
 </dd>
@@ -3915,11 +3849,7 @@ Calendar is available in US production (`api.agentmail.to`) but not yet in EU pr
 <dd>
 
 ```typescript
-await client.inboxes.calendar.getAgenda("scheduler@agentmail.to", {
-    after: new Date("2026-10-07T00:00:00.000Z"),
-    before: new Date("2026-10-16T00:00:00.000Z"),
-    limit: 3
-});
+await client.inboxes.apiKeys.update("inbox_id", "api_key_id", {});
 
 ```
 </dd>
@@ -3943,7 +3873,7 @@ await client.inboxes.calendar.getAgenda("scheduler@agentmail.to", {
 <dl>
 <dd>
 
-**request:** `AgentMail.inboxes.GetCalendarAgendaRequest` 
+**api_key_id:** `AgentMail.ApiKeyId` 
     
 </dd>
 </dl>
@@ -3951,7 +3881,15 @@ await client.inboxes.calendar.getAgenda("scheduler@agentmail.to", {
 <dl>
 <dd>
 
-**requestOptions:** `CalendarClient.RequestOptions` 
+**request:** `AgentMail.UpdateApiKeyRequest` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `ApiKeysClient.RequestOptions` 
     
 </dd>
 </dl>
@@ -3963,7 +3901,7 @@ await client.inboxes.calendar.getAgenda("scheduler@agentmail.to", {
 </dl>
 </details>
 
-<details><summary><code>client.inboxes.calendar.<a href="/src/api/resources/inboxes/resources/calendar/client/Client.ts">createEvent</a>(inbox_id, { ...params }) -> AgentMail.CalendarEventMutationResponse</code></summary>
+<details><summary><code>client.inboxes.apiKeys.<a href="/src/api/resources/inboxes/resources/apiKeys/client/Client.ts">delete</a>(inbox_id, api_key_id) -> void</code></summary>
 <dl>
 <dd>
 
@@ -3975,28 +3913,436 @@ await client.inboxes.calendar.getAgenda("scheduler@agentmail.to", {
 <dl>
 <dd>
 
-Creates a one-off or recurring event on the inbox's calendar. Times are wall-clock values in
-`timezone` (the calendar's default time zone if omitted); the response also gives each
-boundary as a UTC instant in `start_at` and `end_at`.
-
-`calendar.event.created` is sent once the event is stored, then `calendar.event.starting`
-and `calendar.event.ending` as each date begins and ends. With `send_invites: true` the
-inbox also emails an invitation to every attendee.
-
-Pass `client_id` to make retries safe: repeating the request with the same `client_id` and
-body returns the original event with status `200` instead of `201`, for as long as the event
-exists.
-
-With `send_invites: true`, each attendee counts as one send against the organization, pod
-and inbox send limits, charged before the event is stored. An over-limit request returns
-`429` `rate_limit_exceeded` and creates nothing. A replay of an earlier create is not
-charged again.
-
-The event's `etag` is the value to send in `If-Match` to make a later update or delete
-conditional. Requires the `calendar_event_create` permission.
-
-Calendar is available in US production (`api.agentmail.to`) but not yet in EU production
-(`api.agentmail.eu`), which returns `403`.
+**CLI:**
+```bash
+agentmail inboxes api-keys delete --inbox-id <inbox_id> --api-key-id <api_key_id>
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.inboxes.apiKeys.delete("inbox_id", "api_key_id");
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**inbox_id:** `AgentMail.InboxId` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**api_key_id:** `AgentMail.ApiKeyId` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `ApiKeysClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+## Inboxes Calendar
+<details><summary><code>client.inboxes.calendar.<a href="/src/api/resources/inboxes/resources/calendar/client/Client.ts">get</a>(inbox_id, { ...params }) -> AgentMail.Calendar</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Gets the inbox's calendar. Every inbox has one calendar, so this works before any event is
+created. Its `etag` (also the `ETag` response header) is the value to send in `If-Match` to
+make an update conditional.
+
+Requires the `calendar_read` permission. Calendar is available in US production
+(`api.agentmail.to`) but not yet in EU production (`api.agentmail.eu`), which returns `403`.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.inboxes.calendar.get("scheduler@agentmail.to");
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**inbox_id:** `AgentMail.InboxId` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request:** `AgentMail.inboxes.GetCalendarRequest` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `CalendarClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.inboxes.calendar.<a href="/src/api/resources/inboxes/resources/calendar/client/Client.ts">update</a>(inbox_id, { ...params }) -> AgentMail.Calendar</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Updates the calendar's default time zone. Existing events keep their own `timezone`; only
+events created later without a `timezone` use the new default.
+
+Requires the `calendar_update` permission. To make the update conditional, send the
+calendar's current `etag` in `If-Match`: a stale value returns `412`. Without `If-Match` the
+update applies to the calendar as it is.
+
+Calendar is available in US production (`api.agentmail.to`) but not yet in EU production
+(`api.agentmail.eu`), which returns `403`.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.inboxes.calendar.update("scheduler@agentmail.to", {
+    timezone: "America/New_York"
+});
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**inbox_id:** `AgentMail.InboxId` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request:** `AgentMail.inboxes.UpdateCalendarRequestWrapper` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `CalendarClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.inboxes.calendar.<a href="/src/api/resources/inboxes/resources/calendar/client/Client.ts">listEvents</a>(inbox_id, { ...params }) -> AgentMail.ListCalendarEventsResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Lists the events stored on the calendar: one item per one-off or recurring event, plus one
+item for each edited date of a recurring event (as that dated event, with
+`is_exception: true`). Ordered by most recently updated, and cancelled events are included.
+Use it to sync or manage what you created. To see what is on the calendar in a time window,
+use Get Agenda.
+
+The list is always read in the region that serves the request, so it can trail a change made
+moments earlier by a few seconds. Requires the `calendar_event_read` permission.
+
+Calendar is available in US production (`api.agentmail.to`) but not yet in EU production
+(`api.agentmail.eu`), which returns `403`.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.inboxes.calendar.listEvents("scheduler@agentmail.to", {
+    limit: 50
+});
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**inbox_id:** `AgentMail.InboxId` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request:** `AgentMail.inboxes.ListCalendarEventsRequest` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `CalendarClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.inboxes.calendar.<a href="/src/api/resources/inboxes/resources/calendar/client/Client.ts">getAgenda</a>(inbox_id, { ...params }) -> AgentMail.ListCalendarEventsResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Lists every date on the calendar in a time window, ordered by start time: one-off events,
+and recurring events expanded into their individual dates, with cancelled dates left out.
+Use it to answer "what is on the calendar".
+
+The window defaults to now through 90 days from now and can be at most 366 days. Items omit
+`description`, `metadata` and `attendees`; get an event by ID for the full object. An item
+the inbox is invited to still carries `response_status`, so `needs_action` marks an
+invitation waiting for a reply. Dates of
+recurring events appear only up to about 90 days from now; use List Event Instances for a
+recurring event's later dates. While a recurring event's dates are being regenerated after a
+schedule change, which takes a few seconds, the agenda can briefly leave out some of them;
+dates that have already started or ended stay as they ran.
+
+The agenda is read in the region that serves the request, so it can trail a change made
+moments earlier by a few seconds. Pass `consistency=primary` to read your own change right
+away. Requires the `calendar_event_read` permission.
+
+Calendar is available in US production (`api.agentmail.to`) but not yet in EU production
+(`api.agentmail.eu`), which returns `403`.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.inboxes.calendar.getAgenda("scheduler@agentmail.to", {
+    after: new Date("2026-10-07T00:00:00.000Z"),
+    before: new Date("2026-10-16T00:00:00.000Z"),
+    limit: 3
+});
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**inbox_id:** `AgentMail.InboxId` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request:** `AgentMail.inboxes.GetCalendarAgendaRequest` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `CalendarClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.inboxes.calendar.<a href="/src/api/resources/inboxes/resources/calendar/client/Client.ts">createEvent</a>(inbox_id, { ...params }) -> AgentMail.CalendarEventMutationResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Creates a one-off or recurring event on the inbox's calendar. Times are wall-clock values in
+`timezone` (the calendar's default time zone if omitted); the response also gives each
+boundary as a UTC instant in `start_at` and `end_at`.
+
+`calendar.event.created` is sent once the event is stored, then `calendar.event.starting`
+and `calendar.event.ending` as each date begins and ends. With `send_invites: true` the
+inbox also emails an invitation to every attendee.
+
+Pass `client_id` to make retries safe: repeating the request with the same `client_id` and
+body returns the original event with status `200` instead of `201`, for as long as the event
+exists.
+
+With `send_invites: true`, each attendee counts as one send against the organization, pod
+and inbox send limits, charged before the event is stored. An over-limit request returns
+`429` `rate_limit_exceeded` and creates nothing. A replay of an earlier create is not
+charged again.
+
+The event's `etag` is the value to send in `If-Match` to make a later update or delete
+conditional. Requires the `calendar_event_create` permission.
+
+Calendar is available in US production (`api.agentmail.to`) but not yet in EU production
+(`api.agentmail.eu`), which returns `403`.
 </dd>
 </dl>
 </dd>
@@ -5312,8 +5658,240 @@ Returns `409` if the bytes haven't been uploaded yet, or if what was uploaded do
 and `sha256`. Returns `404` for a file that has expired or was deleted, including a pending file not
 completed within a day of its creation.
 
-Requires the `file_create` permission. Only a key with `file_read`, or the key that created the file, can
-complete it; any other key gets `404`.
+Requires the `file_create` permission. Only a key with `file_read`, or the key that created the file, can
+complete it; any other key gets `404`.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.inboxes.files.complete("reports@agentmail.to", "6f1c2f4e-8d3b-4a5e-9c7d-1b2a3c4d5e6f");
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**inbox_id:** `AgentMail.InboxId` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**file_id:** `AgentMail.FileId` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `FilesClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.inboxes.files.<a href="/src/api/resources/inboxes/resources/files/client/Client.ts">get</a>(inbox_id, file_id) -> AgentMail.File_</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Gets a file. A `ready` file comes with a fresh `download_url`, valid for up to an hour.
+
+A get reads the region that serves the request, so for about a second after a delete it can still return
+the deleted file. A file that has expired returns `404` at once.
+
+Requires the `file_read` permission.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.inboxes.files.get("reports@agentmail.to", "6f1c2f4e-8d3b-4a5e-9c7d-1b2a3c4d5e6f");
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**inbox_id:** `AgentMail.InboxId` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**file_id:** `AgentMail.FileId` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `FilesClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.inboxes.files.<a href="/src/api/resources/inboxes/resources/files/client/Client.ts">list</a>(inbox_id, { ...params }) -> AgentMail.ListFilesResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Lists the inbox's files in path order, pending ones included, optionally only those whose path starts with
+`path_prefix`. A prefix matches characters, not whole segments: `reports/q` matches `reports/q3.pdf`. Items
+carry no download URL; get a file for one.
+
+The list is read in the region that serves the request, so a file created or deleted a moment ago may not
+show yet. Expired files never show.
+
+Requires the `file_read` permission.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.inboxes.files.list("reports@agentmail.to", {
+    pathPrefix: "reports/"
+});
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**inbox_id:** `AgentMail.InboxId` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request:** `AgentMail.inboxes.ListFilesRequest` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `FilesClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.inboxes.files.<a href="/src/api/resources/inboxes/resources/files/client/Client.ts">delete</a>(inbox_id, file_id) -> void</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Deletes a file, pending or `ready`, and frees its path at once. Its bytes are deleted, and its space given
+back to the organization's quota, within seconds. A download URL signed before the delete keeps working
+until it expires, at most an hour. Deleting a file that is already gone returns `404`.
+
+Requires the `file_delete` permission. Only a key with `file_read`, or the key that created the file, can
+delete it; any other key gets `404`.
 </dd>
 </dl>
 </dd>
@@ -5328,7 +5906,7 @@ complete it; any other key gets `404`.
 <dd>
 
 ```typescript
-await client.inboxes.files.complete("reports@agentmail.to", "6f1c2f4e-8d3b-4a5e-9c7d-1b2a3c4d5e6f");
+await client.inboxes.files.delete("reports@agentmail.to", "6f1c2f4e-8d3b-4a5e-9c7d-1b2a3c4d5e6f");
 
 ```
 </dd>
@@ -5372,7 +5950,8 @@ await client.inboxes.files.complete("reports@agentmail.to", "6f1c2f4e-8d3b-4a5e-
 </dl>
 </details>
 
-<details><summary><code>client.inboxes.files.<a href="/src/api/resources/inboxes/resources/files/client/Client.ts">get</a>(inbox_id, file_id) -> AgentMail.File_</code></summary>
+## Inboxes Forwarding
+<details><summary><code>client.inboxes.forwarding.<a href="/src/api/resources/inboxes/resources/forwarding/client/Client.ts">get</a>(inbox_id) -> AgentMail.Forwarding</code></summary>
 <dl>
 <dd>
 
@@ -5384,12 +5963,13 @@ await client.inboxes.files.complete("reports@agentmail.to", "6f1c2f4e-8d3b-4a5e-
 <dl>
 <dd>
 
-Gets a file. A `ready` file comes with a fresh `download_url`, valid for up to an hour.
-
-A get reads the region that serves the request, so for about a second after a delete it can still return
-the deleted file. A file that has expired returns `404` at once.
+Get the forwarding this inbox sets. When the inbox sets nothing, `destinations` is `null` and
+the inbox uses its pod's forwarding, or the organization's when the pod sets none.
 
-Requires the `file_read` permission.
+**CLI:**
+```bash
+agentmail inboxes forwarding get --inbox-id <inbox_id>
+```
 </dd>
 </dl>
 </dd>
@@ -5404,7 +5984,7 @@ Requires the `file_read` permission.
 <dd>
 
 ```typescript
-await client.inboxes.files.get("reports@agentmail.to", "6f1c2f4e-8d3b-4a5e-9c7d-1b2a3c4d5e6f");
+await client.inboxes.forwarding.get("inbox_id");
 
 ```
 </dd>
@@ -5428,15 +6008,7 @@ await client.inboxes.files.get("reports@agentmail.to", "6f1c2f4e-8d3b-4a5e-9c7d-
 <dl>
 <dd>
 
-**file_id:** `AgentMail.FileId` 
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**requestOptions:** `FilesClient.RequestOptions` 
+**requestOptions:** `ForwardingClient.RequestOptions` 
     
 </dd>
 </dl>
@@ -5448,7 +6020,7 @@ await client.inboxes.files.get("reports@agentmail.to", "6f1c2f4e-8d3b-4a5e-9c7d-
 </dl>
 </details>
 
-<details><summary><code>client.inboxes.files.<a href="/src/api/resources/inboxes/resources/files/client/Client.ts">list</a>(inbox_id, { ...params }) -> AgentMail.ListFilesResponse</code></summary>
+<details><summary><code>client.inboxes.forwarding.<a href="/src/api/resources/inboxes/resources/forwarding/client/Client.ts">update</a>(inbox_id, { ...params }) -> AgentMail.UpdateForwardingResponse</code></summary>
 <dl>
 <dd>
 
@@ -5460,14 +6032,15 @@ await client.inboxes.files.get("reports@agentmail.to", "6f1c2f4e-8d3b-4a5e-9c7d-
 <dl>
 <dd>
 
-Lists the inbox's files in path order, pending ones included, optionally only those whose path starts with
-`path_prefix`. A prefix matches characters, not whole segments: `reports/q` matches `reports/q3.pdf`. Items
-carry no download URL; get a file for one.
-
-The list is read in the region that serves the request, so a file created or deleted a moment ago may not
-show yet. Expired files never show.
+Set the addresses this inbox forwards to. The list replaces the inbox's current one and any pod
+or organization list for this inbox; lists are never combined. Send an empty list to stop this
+inbox forwarding even when its pod or the organization forwards. An address that is not
+verified is saved but receives nothing until it is verified.
 
-Requires the `file_read` permission.
+**CLI:**
+```bash
+agentmail inboxes forwarding update --inbox-id <inbox_id> --destinations ops@example.com
+```
 </dd>
 </dl>
 </dd>
@@ -5482,8 +6055,8 @@ Requires the `file_read` permission.
 <dd>
 
 ```typescript
-await client.inboxes.files.list("reports@agentmail.to", {
-    pathPrefix: "reports/"
+await client.inboxes.forwarding.update("inbox_id", {
+    destinations: ["destinations", "destinations"]
 });
 
 ```
@@ -5508,7 +6081,7 @@ await client.inboxes.files.list("reports@agentmail.to", {
 <dl>
 <dd>
 
-**request:** `AgentMail.inboxes.ListFilesRequest` 
+**request:** `AgentMail.UpdateForwardingRequest` 
     
 </dd>
 </dl>
@@ -5516,7 +6089,7 @@ await client.inboxes.files.list("reports@agentmail.to", {
 <dl>
 <dd>
 
-**requestOptions:** `FilesClient.RequestOptions` 
+**requestOptions:** `ForwardingClient.RequestOptions` 
     
 </dd>
 </dl>
@@ -5528,7 +6101,7 @@ await client.inboxes.files.list("reports@agentmail.to", {
 </dl>
 </details>
 
-<details><summary><code>client.inboxes.files.<a href="/src/api/resources/inboxes/resources/files/client/Client.ts">delete</a>(inbox_id, file_id) -> void</code></summary>
+<details><summary><code>client.inboxes.forwarding.<a href="/src/api/resources/inboxes/resources/forwarding/client/Client.ts">delete</a>(inbox_id) -> AgentMail.Forwarding</code></summary>
 <dl>
 <dd>
 
@@ -5540,12 +6113,13 @@ await client.inboxes.files.list("reports@agentmail.to", {
 <dl>
 <dd>
 
-Deletes a file, pending or `ready`, and frees its path at once. Its bytes are deleted, and its space given
-back to the organization's quota, within seconds. A download URL signed before the delete keeps working
-until it expires, at most an hour. Deleting a file that is already gone returns `404`.
+Remove this inbox's own forwarding, so the inbox uses its pod's or the organization's forwarding
+again. Verified addresses stay verified. Returns `not_found` when the inbox sets no forwarding.
 
-Requires the `file_delete` permission. Only a key with `file_read`, or the key that created the file, can
-delete it; any other key gets `404`.
+**CLI:**
+```bash
+agentmail inboxes forwarding delete --inbox-id <inbox_id>
+```
 </dd>
 </dl>
 </dd>
@@ -5560,7 +6134,7 @@ delete it; any other key gets `404`.
 <dd>
 
 ```typescript
-await client.inboxes.files.delete("reports@agentmail.to", "6f1c2f4e-8d3b-4a5e-9c7d-1b2a3c4d5e6f");
+await client.inboxes.forwarding.delete("inbox_id");
 
 ```
 </dd>
@@ -5584,15 +6158,7 @@ await client.inboxes.files.delete("reports@agentmail.to", "6f1c2f4e-8d3b-4a5e-9c
 <dl>
 <dd>
 
-**file_id:** `AgentMail.FileId` 
-    
-</dd>
-</dl>
-
-<dl>
-<dd>
-
-**requestOptions:** `FilesClient.RequestOptions` 
+**requestOptions:** `ForwardingClient.RequestOptions` 
     
 </dd>
 </dl>
@@ -10661,6 +11227,227 @@ await client.pods.drafts.getAttachment("pod_id", "draft_id", "attachment_id");
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+## Pods Forwarding
+<details><summary><code>client.pods.forwarding.<a href="/src/api/resources/pods/resources/forwarding/client/Client.ts">get</a>(pod_id) -> AgentMail.Forwarding</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Get the forwarding this pod sets. Its inboxes that set no forwarding of their own use this
+list. When the pod sets nothing, `destinations` is `null` and the pod uses the organization's
+forwarding.
+
+**CLI:**
+```bash
+agentmail pods forwarding get --pod-id <pod_id>
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.pods.forwarding.get("pod_id");
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**pod_id:** `AgentMail.PodId` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `ForwardingClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.pods.forwarding.<a href="/src/api/resources/pods/resources/forwarding/client/Client.ts">update</a>(pod_id, { ...params }) -> AgentMail.UpdateForwardingResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Set the addresses this pod forwards to. The list replaces the pod's current one and the
+organization's list for this pod; lists are never combined. Send an empty list to stop
+forwarding in this pod even when the organization forwards. An address that is not verified is
+saved but receives nothing until it is verified.
+
+**CLI:**
+```bash
+agentmail pods forwarding update --pod-id <pod_id> --destinations ops@example.com
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.pods.forwarding.update("pod_id", {
+    destinations: ["destinations", "destinations"]
+});
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**pod_id:** `AgentMail.PodId` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request:** `AgentMail.UpdateForwardingRequest` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `ForwardingClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.pods.forwarding.<a href="/src/api/resources/pods/resources/forwarding/client/Client.ts">delete</a>(pod_id) -> AgentMail.Forwarding</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Remove this pod's own forwarding, so the pod uses the organization's forwarding again. Verified
+addresses stay verified. Returns `not_found` when the pod sets no forwarding.
+
+**CLI:**
+```bash
+agentmail pods forwarding delete --pod-id <pod_id>
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.pods.forwarding.delete("pod_id");
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**pod_id:** `AgentMail.PodId` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `ForwardingClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>