@naturali/sdk 0.125.0 → 0.126.0

package/dist/index.cjs

@@ -3648,6 +3648,34 @@ var Projects = class {
 			...options
 		});
 	}
+	/**
+	* List project usage events
+	*
+	* The rows a rollup summed — one per metered occurrence, most recent first. Takes the same narrowings [the meter](/docs/api/projects/get-project-usage) does, so a query that produced a bucket answers here unchanged and reads back what went into it. This is the audit and reconciliation view: what was measured, when, against which agent, session, actor and provider, and what each component was priced at.
+	*
+	* An id naming nothing in this project yields an empty page rather than dropping the filter, so a mistyped narrowing can never widen the list past what was asked for.
+	*
+	*/
+	static listProjectUsageEvents(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/usage/events",
+			...options
+		});
+	}
+	/**
+	* Get a generation or orchestration-run billing receipt
+	*
+	* What one occurrence was billed, line by line: per-event line items with their measured components and unit prices, a per-meter-type split, and the totals. Pass generation_id for one generation, or orchestration_run_id for a receipt summed across every event the run metered. Exactly one of the two is required.
+	*
+	* This is the itemisation behind a single number — where [the meter](/docs/api/projects/get-project-usage) says a window cost $12.40, a receipt says which components of which call made up one occurrence of it. On an orchestration-run receipt every line carries node_id, so grouping by it gives the per-node cost the total hides; a retried node contributes one line per attempt, which is the intended reading for spend.
+	*
+	*/
+	static getProjectUsageReceipt(options) {
+		return (options.client ?? client).get({
+			url: "/v1/projects/{project_id}/usage/receipt",
+			...options
+		});
+	}
 };
 var Quotas = class {
 	/**