@naturali/sdk 0.180.0 → 0.182.0

package/dist/index.cjs

@@ -1142,6 +1142,18 @@ var Admin = class {
 		});
 	}
 	/**
+	* Read a user's usage this billing cycle
+	*
+	* The same answer `GET /v1/users/me/usage` gives the account itself: runs, indexed storage and the plan-capped counts, per project and against the rung. Needs the `admin` role.
+	*
+	*/
+	static getUserUsage(options) {
+		return (options.client ?? client).get({
+			url: "/v1/admin/users/{user_id}/usage",
+			...options
+		});
+	}
+	/**
 	* Read the global price book
 	*
 	* The upstream runtime's global default prices — the rows carrying neither a provider nor a project, which is all the upstream listing returns, so no tenant's own rates appear here.
@@ -1485,6 +1497,7 @@ var AiProviders = class {
 	* Listing resolves credentials the same way generation does, so a record that can generate can list. The API-key types (`openai`, `groq`, `xai`, `gateway`, `custom`, `anthropic`, `google`) use the record's linked secret and cannot list without one. `bedrock` and `vertex` use the linked secret — IAM keys or a Bedrock API key, a Google service-account key. A record with no `secret_id` would fall back to the server's own credentials (the AWS default credential chain, Google Application Default Credentials); it can list only on a deployment that allows a record to use them, and returns `400 AI_PROVIDER_MISCONFIGURED` otherwise.
 	* A Vertex record needs no `config.project` when its secret is a service-account key, since the key file names its own project. A Vertex record in express mode (API key) cannot list at all: the publisher-model listing rejects API keys and needs a credential that asserts a principal, so it returns `400 MODEL_LISTING_UNSUPPORTED`.
 	* The Vertex answer is the publisher catalogue the record's `config.location` region serves. The project behind the credential is billed and quota'd for the call but does not filter the result, so a listed model may still be unavailable to that project at generation time.
+	* The provider answers its whole catalogue in one call; `q`, `limit` and `offset` narrow and page what it returned. A request without `limit` gets the first 50 models.
 	*
 	*/
 	static listAiProviderModels(options) {
@@ -1759,6 +1772,34 @@ var Assistant = class {
 		});
 	}
 	/**
+	* Delete a conversation
+	*
+	* Deletes one of your conversations and its messages. What its turns cost stays on your usage.
+	*
+	*/
+	static deleteAssistantSession(options) {
+		return (options.client ?? client).delete({
+			url: "/v1/assistant/sessions/{session_id}",
+			...options
+		});
+	}
+	/**
+	* Rename a conversation
+	*
+	* Sets the name the conversation is listed by. A name given before the first message is kept.
+	*
+	*/
+	static renameAssistantSession(options) {
+		return (options.client ?? client).patch({
+			url: "/v1/assistant/sessions/{session_id}",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options.headers
+			}
+		});
+	}
+	/**
 	* Read a conversation
 	*
 	* The newest 100 messages of one conversation, oldest first.
@@ -3235,6 +3276,18 @@ var Generations = class {
 		});
 	}
 	/**
+	* List the memory writes a generation made
+	*
+	* Every memory write this turn made, oldest first: each memory rule's firings and the agent's own `write_memory` calls alike. The rows behind the generation's per-rule `extraction` counts. Reading them is reading the generation (`generations:GetGeneration`).
+	*
+	*/
+	static listGenerationMemoryAssertions(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/generations/{generation_id}/memory-assertions",
+			...options
+		});
+	}
+	/**
 	* Get a generation's transcript
 	*
 	* Returns one generation's turn read back as an ordered sequence of steps: what it was asked, each model step with its tool calls and results, and how it ended.
@@ -4183,8 +4236,8 @@ var Orchestrations = class {
 	/**
 	* Get orchestration queue stats
 	*
-	* Returns a point-in-time snapshot of the orchestration run queue: how many tasks are waiting to be claimed (`queue_depth`), how many are currently claimed with a valid lease (`claimed_tasks`), the age of the oldest waiting task, recent claim-latency percentiles over a rolling in-process window, and a per-project breakdown. Intended for admin/operator policies; guarded by `orchestrations:GetQueueStats`.
-	* Every figure is scoped to what the caller may see. A project-scoped caller gets `per_project` for their own projects only, `queue_depth` and `claimed_tasks` summed over those same projects, and `null` for `oldest_queued_age_seconds` and the `claim_latency_ms` percentiles — both describe the whole deployment and cannot be narrowed, so they are withheld rather than approximated. An unrestricted caller (the action granted on every project) gets the deployment-wide figures.
+	* Returns a point-in-time snapshot of the orchestration run queue: how many tasks are waiting to be claimed (`queue_depth`), how many are currently claimed with a valid lease (`claimed_tasks`), the age of the oldest waiting task, recent claim-latency percentiles over a rolling in-process window. The per-project breakdown is listed by `GET /v1/projects/{project_id}/orchestrations/queue/stats/projects`. Intended for admin/operator policies; guarded by `orchestrations:GetQueueStats`.
+	* Every figure is scoped to what the caller may see. A project-scoped caller gets `queue_depth` and `claimed_tasks` summed over their own projects, and `null` for `oldest_queued_age_seconds` and the `claim_latency_ms` percentiles — both describe the whole deployment and cannot be narrowed, so they are withheld rather than approximated. An unrestricted caller (the action granted on every project) gets the deployment-wide figures.
 	*
 	*/
 	static getQueueStats(options) {
@@ -4203,6 +4256,27 @@ var Orchestrations = class {
 		});
 	}
 	/**
+	* List the projects with queued orchestration work
+	*
+	* One row per project with any queued or claimed task, ordered by project ID: the per-project breakdown of `GET /v1/projects/{project_id}/orchestrations/queue/stats`. A project-scoped caller sees its own projects only. Guarded by `orchestrations:GetQueueStats`.
+	*
+	*/
+	static listQueueStatsProjects(options) {
+		return (options.client ?? client).get({
+			security: [{
+				key: "bearerAuth",
+				scheme: "bearer",
+				type: "http"
+			}, {
+				key: "oauth2",
+				scheme: "bearer",
+				type: "http"
+			}],
+			url: "/v1/projects/{project_id}/orchestrations/queue/stats/projects",
+			...options
+		});
+	}
+	/**
 	* Delete an orchestration
 	*
 	* Deletes an orchestration definition and all its runs.
@@ -4376,6 +4450,17 @@ var Orchestrations = class {
 			...options
 		});
 	}
+	/**
+	* List a run's node executions
+	*
+	* The run's per-node execution records, oldest first: one per node attempt, retries and skipped nodes included. Each captures the resolved input, output, status and error of that attempt — the orchestration analogue of an LLM trace. Reading them is reading the run (`orchestrations:GetRun`).
+	*/
+	static listOrchestrationRunNodeExecutions(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/orchestration-runs/{orchestration_run_id}/node-executions",
+			...options
+		});
+	}
 };
 var Projects = class {
 	/**
@@ -5197,7 +5282,7 @@ var Traces = class {
 	/**
 	* Get trace tree
 	*
-	* Returns the full execution tree rooted at the given trace (or its root if the given trace is a child). Each node represents one agent's execution session. The `children` array contains traces triggered by sub-agent tool calls from that trace.
+	* Returns the full execution tree rooted at the given trace (or its root if the given trace is a child). Each node represents one agent's execution session. The `children` array contains traces triggered by sub-agent tool calls from that trace. A node's generations are listed by `GET /v1/projects/{project_id}/generations?trace_id=`, and a node's direct children page by `GET /v1/projects/{project_id}/traces?parent_trace_id=`.
 	*
 	*/
 	static getTraceTree(options) {
@@ -5397,7 +5482,9 @@ var Users = class {
 		});
 	}
 	/**
-	* Get the current account's runs this billing cycle
+	* Get the current account's usage this billing cycle
+	*
+	* What the account uses this billing cycle, per project and against its plan: runs, indexed storage, and the counts the plan caps — projects, active channels and triggers.
 	*
 	* How many runs the account has made this billing cycle, and how many its plan includes. A **run is one agent generation or one tool call** — the unit every rung is priced in. Every tool call counts, including those an agent makes inside a generation; a `client` tool counts nothing.
 	*
@@ -5409,7 +5496,7 @@ var Users = class {
 	*
 	* **This route counts live; the refusal reads a figure counted every few minutes.** So the two can differ by a burst: this is the more current number, and a refusal quotes the one it actually enforced.
 	*
-	* It is also more expensive than the balance read: it asks the meter once per project. Poll it on the order of minutes, not seconds.
+	* It is also more expensive than the balance read: it reads the runtime several times per project. Poll it on the order of minutes, not seconds. A figure that could not be read is `null` rather than failing the request.
 	*
 	*/
 	static getCurrentUserUsage(options) {
@@ -5419,6 +5506,22 @@ var Users = class {
 		});
 	}
 	/**
+	* List the current account's credit ledger
+	*
+	* A cursor page of the account's model-credit ledger, newest first, with the balance the whole ledger sums to. The ledger is append-only: a correction is a new line, never an edit.
+	*
+	* A `usage` line is managed model spend, written as the meter is reconciled every 15 minutes per project, so the ledger grows by a line per project per window that spent anything. Filter with `kind`.
+	*
+	* The other side of a marketplace line is another account's project, so a `fee` or `earned` line names the cycle it settles, not that project.
+	*
+	*/
+	static listCurrentUserCredits(options) {
+		return (options?.client ?? client).get({
+			url: "/v1/users/me/credits",
+			...options
+		});
+	}
+	/**
 	* List what a billing ceiling stopped
 	*
 	* Schedule triggers, eval runs, orchestration runs and workflow tasks the platform stopped on this account's projects because the credit balance went below zero or a Free plan's runs ran out, and that have not been restored or dismissed yet. Newest first.