@athenaintel/sdk 4.3.2243 → 4.3.2245

package/dist/esm/api/resources/databases/client/requests/DatabaseComputeSettingsUpdateRequestIn.d.mts

@@ -0,0 +1,12 @@
+/**
+ * @example
+ *     {
+ *         asset_id: "asset_id",
+ *         suspend_timeout_seconds: 3600
+ *     }
+ */
+export interface DatabaseComputeSettingsUpdateRequestIn {
+    asset_id: string;
+    /** Seconds without activity after which the database suspends (scales to zero). 0 means it never suspends: the compute keeps running, and keeps using capacity, until you change this. Otherwise 60 to 86400 (24 hours). A new database starts with 1800 (30 minutes). The same setting as auto-suspend in the database's Settings in Athena. */
+    suspend_timeout_seconds: number;
+}

package/dist/esm/api/resources/databases/client/requests/DatabaseComputeSettingsUpdateRequestIn.mjs

@@ -0,0 +1,2 @@
+// This file was auto-generated by Fern from our API Definition.
+export {};

package/dist/esm/api/resources/databases/client/requests/GetSettingsDatabasesRequest.d.mts

@@ -0,0 +1,9 @@
+/**
+ * @example
+ *     {
+ *         asset_id: "asset_id"
+ *     }
+ */
+export interface GetSettingsDatabasesRequest {
+    asset_id: string;
+}

package/dist/esm/api/resources/databases/client/requests/GetSettingsDatabasesRequest.mjs

@@ -0,0 +1,2 @@
+// This file was auto-generated by Fern from our API Definition.
+export {};

package/dist/esm/api/resources/databases/client/requests/WakeDatabasesRequest.d.mts

@@ -0,0 +1,9 @@
+/**
+ * @example
+ *     {
+ *         asset_id: "asset_id"
+ *     }
+ */
+export interface WakeDatabasesRequest {
+    asset_id: string;
+}

package/dist/esm/api/resources/databases/client/requests/WakeDatabasesRequest.mjs

@@ -0,0 +1,2 @@
+// This file was auto-generated by Fern from our API Definition.
+export {};

package/dist/esm/api/resources/databases/client/requests/index.d.mts

@@ -1,8 +1,11 @@
+export type { DatabaseComputeSettingsUpdateRequestIn } from "./DatabaseComputeSettingsUpdateRequestIn.mjs";
 export type { DatabaseSqlRequest } from "./DatabaseSqlRequest.mjs";
 export type { DeleteDatabasesRequest } from "./DeleteDatabasesRequest.mjs";
+export type { GetSettingsDatabasesRequest } from "./GetSettingsDatabasesRequest.mjs";
 export type { GetStatusDatabasesRequest } from "./GetStatusDatabasesRequest.mjs";
 export type { GetTableSchemaDatabasesRequest } from "./GetTableSchemaDatabasesRequest.mjs";
 export type { InsertDataRequest } from "./InsertDataRequest.mjs";
 export type { ListTablesDatabasesRequest } from "./ListTablesDatabasesRequest.mjs";
 export type { SelectDatabasesRequest } from "./SelectDatabasesRequest.mjs";
 export type { UpdateDataRequest } from "./UpdateDataRequest.mjs";
+export type { WakeDatabasesRequest } from "./WakeDatabasesRequest.mjs";

package/dist/esm/api/resources/tools/resources/sheets/client/requests/UpdateSheetCellRequest.d.mts

@@ -1,3 +1,4 @@
+import type * as AthenaIntelligence from "../../../../../../index.mjs";
 /**
  * @example
  *     {
@@ -12,6 +13,8 @@ export interface UpdateSheetCellRequest {
     asset_id: string;
     /** 1-based column index (e.g., 1 = column A) */
     column: number;
+    /** Optional cell format (textFormat, backgroundColor, numberFormat, alignment, borders) applied in the same write as the value, like `formatting` on range/update. */
+    formatting?: AthenaIntelligence.CellFormat | null;
     /** 1-based row index (e.g., 1 = first row) */
     row: number;
     /** Sheet ID (defaults to 1) */

package/dist/esm/api/types/ComputerStatusResponseOut.d.mts

@@ -0,0 +1,33 @@
+/**
+ * A computer's live runtime state, read without starting or waking it.
+ */
+export interface ComputerStatusResponseOut {
+    /** The computer asset id. */
+    asset_id: string;
+    /** Set when someone stopped the computer with Stop. While it is `stopping`, `stopped` or `uncertain`, implicit wakes are refused: minting SSH access answers 409 and an SSH connection does not start it. Call `start_computer` to clear it. `null` or `cleared` means no explicit stop is in force. */
+    explicit_stop?: ComputerStatusResponseOut.ExplicitStop | null;
+    /** Why `ready` is false; `null` when it is true. `not_started`: the computer is not running — call `start_computer`. `starting`: it is running and its guest is still coming up — keep polling. `unobservable`: readiness could not be read this time — keep polling. `launcher_outdated`: the computer runs an outdated runtime component that polling will not change — stop it and start it again to update it. */
+    not_ready_reason?: ComputerStatusResponseOut.NotReadyReason | null;
+    /** The computer's runtime provider (e.g. `talos_v2`). */
+    provider?: string | null;
+    /** Whether the computer serves work now: `state` is `started` and the guest answers ready (its workspace attached and its environment applied). Only then do commands, SSH sessions and deployed URLs reach the computer without first waiting for a start. `started` alone can come a few seconds before `ready`. */
+    ready: boolean;
+    /** The runtime's current state: `started` (running; check `ready`), `stopped` (suspended — by idle auto-stop or by Stop; files are kept), `restoring` (a start is in progress), `error` (the runtime failed; start or restart it), or `unknown` (the state could not be read this time; retry). `started`, `stopped` and `error` hold until something changes them; `restoring` and `unknown` are transient. */
+    state: string;
+}
+export declare namespace ComputerStatusResponseOut {
+    const ExplicitStop: {
+        readonly Stopping: "stopping";
+        readonly Stopped: "stopped";
+        readonly Uncertain: "uncertain";
+        readonly Cleared: "cleared";
+    };
+    type ExplicitStop = (typeof ExplicitStop)[keyof typeof ExplicitStop];
+    const NotReadyReason: {
+        readonly NotStarted: "not_started";
+        readonly Starting: "starting";
+        readonly LauncherOutdated: "launcher_outdated";
+        readonly Unobservable: "unobservable";
+    };
+    type NotReadyReason = (typeof NotReadyReason)[keyof typeof NotReadyReason];
+}

package/dist/esm/api/types/ComputerStatusResponseOut.mjs

@@ -0,0 +1,16 @@
+// This file was auto-generated by Fern from our API Definition.
+export var ComputerStatusResponseOut;
+(function (ComputerStatusResponseOut) {
+    ComputerStatusResponseOut.ExplicitStop = {
+        Stopping: "stopping",
+        Stopped: "stopped",
+        Uncertain: "uncertain",
+        Cleared: "cleared",
+    };
+    ComputerStatusResponseOut.NotReadyReason = {
+        NotStarted: "not_started",
+        Starting: "starting",
+        LauncherOutdated: "launcher_outdated",
+        Unobservable: "unobservable",
+    };
+})(ComputerStatusResponseOut || (ComputerStatusResponseOut = {}));

package/dist/esm/api/types/DatabaseComputeSettingsResponseOut.d.mts

@@ -0,0 +1,9 @@
+/**
+ * The database's compute settings that the public API can read and set.
+ */
+export interface DatabaseComputeSettingsResponseOut {
+    /** The database asset ID */
+    asset_id: string;
+    /** Seconds without activity after which the database suspends (scales to zero). 0 means it never suspends: the compute keeps running, and keeps using capacity, until you change this. Otherwise 60 to 86400 (24 hours). A new database starts with 1800 (30 minutes). The same setting as auto-suspend in the database's Settings in Athena. */
+    suspend_timeout_seconds: number;
+}

package/dist/esm/api/types/DatabaseComputeSettingsResponseOut.mjs

@@ -0,0 +1,2 @@
+// This file was auto-generated by Fern from our API Definition.
+export {};

package/dist/esm/api/types/DatabaseStatusResponse.d.mts

@@ -11,6 +11,8 @@ export interface DatabaseStatusResponse {
     message?: string | null;
     /** Database provider ('kronos') */
     provider: string;
+    /** Why the compute is in this state, when the control plane says: `ComputeUnschedulable` on a `suspended` database means no node could host its compute size, so a wake only restarts the same wait; choose a smaller compute size in the database's Settings in Athena first. Absent on older control planes. */
+    reason?: string | null;
     /** Standardized database status */
     status: DatabaseStatusResponse.Status;
 }

package/dist/esm/api/types/DatabaseWakeResponseOut.d.mts

@@ -0,0 +1,19 @@
+/**
+ * Response for a wake request.
+ */
+export interface DatabaseWakeResponseOut {
+    /** The database asset ID */
+    asset_id: string;
+    /** Optional detail from the control plane */
+    message?: string | null;
+    /** `running`: the compute was already running; its idle clock was reset. `starting`: the compute is starting; poll `GET /databases/{asset_id}/compute-status` until it reports `running`. */
+    status: DatabaseWakeResponseOut.Status;
+}
+export declare namespace DatabaseWakeResponseOut {
+    /** `running`: the compute was already running; its idle clock was reset. `starting`: the compute is starting; poll `GET /databases/{asset_id}/compute-status` until it reports `running`. */
+    const Status: {
+        readonly Running: "running";
+        readonly Starting: "starting";
+    };
+    type Status = (typeof Status)[keyof typeof Status];
+}

package/dist/esm/api/types/DatabaseWakeResponseOut.mjs

@@ -0,0 +1,9 @@
+// This file was auto-generated by Fern from our API Definition.
+export var DatabaseWakeResponseOut;
+(function (DatabaseWakeResponseOut) {
+    /** `running`: the compute was already running; its idle clock was reset. `starting`: the compute is starting; poll `GET /databases/{asset_id}/compute-status` until it reports `running`. */
+    DatabaseWakeResponseOut.Status = {
+        Running: "running",
+        Starting: "starting",
+    };
+})(DatabaseWakeResponseOut || (DatabaseWakeResponseOut = {}));

package/dist/esm/api/types/index.d.mts

@@ -41,6 +41,7 @@ export * from "./CollabAgentSendMessageResponseOut.mjs";
 export * from "./CollabTokenResponse.mjs";
 export * from "./ComputerInitializationResponse.mjs";
 export * from "./ComputerLifecycleResponseOut.mjs";
+export * from "./ComputerStatusResponseOut.mjs";
 export * from "./ConversationAssetInfo.mjs";
 export * from "./ConversationMessage.mjs";
 export * from "./ConversationResult.mjs";
@@ -51,6 +52,7 @@ export * from "./CreateAssetResponseOut.mjs";
 export * from "./CreateNewSheetTabResponse.mjs";
 export * from "./CreateProjectResponseOut.mjs";
 export * from "./DatabaseColumnInfo.mjs";
+export * from "./DatabaseComputeSettingsResponseOut.mjs";
 export * from "./DatabaseDataResponse.mjs";
 export * from "./DatabaseMutationResponse.mjs";
 export * from "./DatabaseSqlResponse.mjs";
@@ -58,6 +60,7 @@ export * from "./DatabaseStatusResponse.mjs";
 export * from "./DatabaseTableInfo.mjs";
 export * from "./DatabaseTableSchemaResponse.mjs";
 export * from "./DatabaseTablesResponse.mjs";
+export * from "./DatabaseWakeResponseOut.mjs";
 export * from "./DataFrameRequestOut.mjs";
 export * from "./DataFrameUnknownFormatError.mjs";
 export * from "./DefaultVisibility.mjs";

package/dist/esm/api/types/index.mjs

@@ -41,6 +41,7 @@ export * from "./CollabAgentSendMessageResponseOut.mjs";
 export * from "./CollabTokenResponse.mjs";
 export * from "./ComputerInitializationResponse.mjs";
 export * from "./ComputerLifecycleResponseOut.mjs";
+export * from "./ComputerStatusResponseOut.mjs";
 export * from "./ConversationAssetInfo.mjs";
 export * from "./ConversationMessage.mjs";
 export * from "./ConversationResult.mjs";
@@ -51,6 +52,7 @@ export * from "./CreateAssetResponseOut.mjs";
 export * from "./CreateNewSheetTabResponse.mjs";
 export * from "./CreateProjectResponseOut.mjs";
 export * from "./DatabaseColumnInfo.mjs";
+export * from "./DatabaseComputeSettingsResponseOut.mjs";
 export * from "./DatabaseDataResponse.mjs";
 export * from "./DatabaseMutationResponse.mjs";
 export * from "./DatabaseSqlResponse.mjs";
@@ -58,6 +60,7 @@ export * from "./DatabaseStatusResponse.mjs";
 export * from "./DatabaseTableInfo.mjs";
 export * from "./DatabaseTableSchemaResponse.mjs";
 export * from "./DatabaseTablesResponse.mjs";
+export * from "./DatabaseWakeResponseOut.mjs";
 export * from "./DataFrameRequestOut.mjs";
 export * from "./DataFrameUnknownFormatError.mjs";
 export * from "./DefaultVisibility.mjs";

package/dist/esm/version.d.mts

@@ -1 +1 @@
-export declare const SDK_VERSION = "4.3.2243";
+export declare const SDK_VERSION = "4.3.2245";

package/dist/esm/version.mjs

@@ -1 +1 @@
-export const SDK_VERSION = "4.3.2243";
+export const SDK_VERSION = "4.3.2245";

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@athenaintel/sdk",
-    "version": "4.3.2243",
+    "version": "4.3.2245",
     "private": false,
     "repository": "github:Athena-Intel/athena-typescript",
     "type": "commonjs",

package/reference.md

@@ -648,7 +648,7 @@ await client.assets.convertExcelToSheet({
 <dl>
 <dd>
 
-Create a new asset such as a spreadsheet, document, folder, database, computer, user interface, skill, collab agent, or generic doc (admin-only) in your workspace with your current permissions. Computer assets return 202 after durable submission, which commits the asset and initialization delivery intent together. Runtime provisioning continues asynchronously. Inspect the returned asset ID for progress instead of repeating creation. Computers accept the same configuration as the Athena UI's creation dialog: template, provider, cpu, memory (GiB), disk (GiB) and env_vars. Sizes must be offered by the environment's computer resource policy, and only admins may pick a size other than the template default (403 otherwise). In capability enforce mode, computer creation requires computer.create and returns 403 when denied.
+Create a new asset such as a spreadsheet, document, folder, database, computer, user interface, skill, collab agent, or generic doc (admin-only) in your workspace with your current permissions. Computer assets return 202 after durable submission, which commits the asset and initialization delivery intent together. Runtime provisioning continues asynchronously. Inspect the returned asset ID for progress instead of repeating creation. Computers accept the same configuration as the Athena UI's creation dialog: template, provider, cpu, memory (GiB), disk (GiB) and env_vars. Sizes must be offered by the environment's computer resource policy, and only admins may pick a size other than the template default (403 otherwise). In capability enforce mode, computer creation requires computer.create and returns 403 when denied. Databases accept suspend_timeout_seconds, the auto-suspend window from the database's Settings in Athena: 0 keeps the database running (it never suspends, and keeps using capacity), otherwise 60 to 86400 seconds. A database is provisioned in the background: poll GET /api/v0/databases/{asset_id}/compute-status until it reports running or suspended.
 </dd>
 </dl>
 </dd>
@@ -1991,7 +1991,7 @@ await client.computer.getSshAccess({
 <dl>
 <dd>
 
-Generate a time-limited SSH access token for a computer asset. Returns a full SSH command and token that can be used to connect to the computer's underlying VM and run commands. The computer must support SSH access and be in a running state.
+Generate a time-limited SSH access token for a computer asset. Returns a full SSH command and token that can be used to connect to the computer's underlying VM and run commands. The computer must support SSH access. If it is stopped, this call starts it first and can take as long as `start_computer`; after an explicit Stop it returns 409 until you call `start_computer`. Use `get_status` to see whether the computer is ready.
 </dd>
 </dl>
 </dd>
@@ -2254,7 +2254,7 @@ await client.computer.revokeSshAccessToken({
 <dl>
 <dd>
 
-Start a stopped computer's runtime and wait for it to come up — the same operation as the Start button in Athena. Idempotent for a running computer. Returns 409 when the computer's provider does not support lifecycle operations.
+Start a stopped computer's runtime and wait for it to come up — the same operation as the Start button in Athena. Idempotent for a running computer, and it clears an explicit stop. `state` is `started` once the runtime is up; the guest can need a few more seconds, so poll `get_status` until `ready` is true before you rely on commands or SSH. A proxy in front of the API can end this request after about 60 seconds while the start continues on the server; then poll `get_status`. Returns 409 when the computer's provider does not support lifecycle operations.
 </dd>
 </dl>
 </dd>
@@ -2303,6 +2303,79 @@ await client.computer.startComputer({
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.computer.<a href="/src/api/resources/computer/client/Client.ts">getStatus</a>({ ...params }) -> AthenaIntelligence.ComputerStatusResponseOut</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Read an existing computer's live runtime state and whether it is ready, without starting, waking, or repairing it. Works for every computer, including those created before durable initialization (`get_initialization` reports creation-time progress only). Requires membership in the computer's workspace and VIEW access. This read does not count as activity, so polling it does not keep the computer awake.
+
+**Waiting for a computer.** Call `start_computer`, then poll this endpoint every few seconds until `ready` is true; stop polling when `not_ready_reason` is `launcher_outdated`. `start_computer` waits for the computer, but a proxy in front of the API can end a long request (about 60 seconds on Athena's ingress) while the start continues on the server. The server waits up to 210 seconds by default for the computer's runtime to boot before it reports a failure, and Athena alerts its operators when the 90th percentile of starts goes above 3 minutes.
+
+**Auto-stop.** A computer stops after its `auto_stop_minutes` of inactivity (60 minutes unless the computer or the deployment sets another value; 0 means it never stops on its own). Activity is work inside the computer — commands, terminal and SSH sessions, file operations — and requests to its deployed URLs. Status reads are not activity.
+
+**The asset record's `status`.** The computer's `status` in `GET /assets/{asset_id}` records the last lifecycle change Athena recorded (create, Start, Stop); it is not a live read. It can read `running` while the computer is stopped, for example after an idle auto-stop, or `stopped` after something woke it. Use this endpoint for the live state.
+
+Returns 403 when the caller is not a member of the computer's workspace, 409 while the computer is still being created or when its creation failed, 404 when the asset does not exist or its runtime is gone for good (stop polling), and 502 when the runtime could not be read (retry).
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.computer.getStatus({
+    asset_id: "asset_id"
+});
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**request:** `AthenaIntelligence.GetStatusComputerRequest` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `ComputerClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>
@@ -2389,10 +2462,13 @@ Check if a database is running, suspended, or starting up. Poll this endpoint to
 
 **Status Values:**
 - `running` - Database is active and accepting connections
-- `suspended` - Database is suspended (scale-to-zero), will auto-resume on first query
-- `starting` - Database is waking up
-- `failed` - Database failed to start
-- `unknown` - Status could not be determined
+- `suspended` - Database is suspended (scale-to-zero). It wakes on `POST /databases/{asset_id}/wake` or on the first SQL request. When `reason` is `ComputeUnschedulable`, no node could host its compute size: waking it only restarts the same wait
+- `starting` - Database is waking up, or its compute is being recreated
+- `creating` - Database is being created; it has no compute yet
+- `failed` - Database failed to start, or its creation failed (`message` says which)
+- `unknown` - Status could not be determined (the control plane did not answer); retry
+
+A database suspends (scales to zero) after `suspend_timeout_seconds` without activity; `GET`/`PATCH /databases/{asset_id}/settings` read and set that window, and 0 keeps it running. Reading the compute status or the settings never wakes a suspended database. Two things do: `POST /databases/{asset_id}/wake`, which answers at once while the compute starts, or any request that runs SQL on it, such as `POST /databases/{asset_id}/sql`, which waits for the compute up to 120 seconds; if the compute is still starting then, the answer is 503 with `Retry-After` and the statement did not run. A cold start usually takes 30 seconds to 2 minutes.
 </dd>
 </dl>
 </dd>
@@ -2889,6 +2965,141 @@ await client.databases.getTableSchema({
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.databases.<a href="/src/api/resources/databases/client/Client.ts">getSettings</a>({ ...params }) -> AthenaIntelligence.DatabaseComputeSettingsResponseOut</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Read the database's auto-suspend window, the same setting as auto-suspend in the database's Settings in Athena. Reading never wakes the database.
+
+A database suspends (scales to zero) after `suspend_timeout_seconds` without activity; `GET`/`PATCH /databases/{asset_id}/settings` read and set that window, and 0 keeps it running. Reading the compute status or the settings never wakes a suspended database. Two things do: `POST /databases/{asset_id}/wake`, which answers at once while the compute starts, or any request that runs SQL on it, such as `POST /databases/{asset_id}/sql`, which waits for the compute up to 120 seconds; if the compute is still starting then, the answer is 503 with `Retry-After` and the statement did not run. A cold start usually takes 30 seconds to 2 minutes.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.databases.getSettings({
+    asset_id: "asset_id"
+});
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**request:** `AthenaIntelligence.GetSettingsDatabasesRequest` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `DatabasesClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.databases.<a href="/src/api/resources/databases/client/Client.ts">updateSettings</a>({ ...params }) -> AthenaIntelligence.DatabaseComputeSettingsResponseOut</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Set the database's auto-suspend window: 0 keeps the database running (it never suspends, and keeps using compute capacity), otherwise 60 to 86400 seconds. The same setting, values and edit-access rule as auto-suspend in the database's Settings in Athena; the change applies at once and does not restart or wake the database.
+
+A database suspends (scales to zero) after `suspend_timeout_seconds` without activity; `GET`/`PATCH /databases/{asset_id}/settings` read and set that window, and 0 keeps it running. Reading the compute status or the settings never wakes a suspended database. Two things do: `POST /databases/{asset_id}/wake`, which answers at once while the compute starts, or any request that runs SQL on it, such as `POST /databases/{asset_id}/sql`, which waits for the compute up to 120 seconds; if the compute is still starting then, the answer is 503 with `Retry-After` and the statement did not run. A cold start usually takes 30 seconds to 2 minutes.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.databases.updateSettings({
+    asset_id: "asset_id",
+    suspend_timeout_seconds: 3600
+});
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**request:** `AthenaIntelligence.DatabaseComputeSettingsUpdateRequestIn` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `DatabasesClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>
@@ -2955,6 +3166,73 @@ await client.databases.executeSql({
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.databases.<a href="/src/api/resources/databases/client/Client.ts">wake</a>({ ...params }) -> AthenaIntelligence.DatabaseWakeResponseOut</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Start a suspended database's compute and answer at once, without waiting for it to run. Poll `GET /databases/{asset_id}/compute-status` until it reports `running`. Waking a running database resets its idle clock and answers 200 with `running`, so it is safe to call before every batch of work. The same action as Resume Database in Athena; it needs edit access to the database.
+
+A database suspends (scales to zero) after `suspend_timeout_seconds` without activity; `GET`/`PATCH /databases/{asset_id}/settings` read and set that window, and 0 keeps it running. Reading the compute status or the settings never wakes a suspended database. Two things do: `POST /databases/{asset_id}/wake`, which answers at once while the compute starts, or any request that runs SQL on it, such as `POST /databases/{asset_id}/sql`, which waits for the compute up to 120 seconds; if the compute is still starting then, the answer is 503 with `Retry-After` and the statement did not run. A cold start usually takes 30 seconds to 2 minutes.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```typescript
+await client.databases.wake({
+    asset_id: "asset_id"
+});
+
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**request:** `AthenaIntelligence.WakeDatabasesRequest` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**requestOptions:** `DatabasesClient.RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>