v5

OpenAPI 3.1.02026-08-025631,1012.8 MB

Cluster Executions

Rename Cluster Labels (Per-Execution)

Rename cluster labels for a single execution — no re-run required.

Entries merge into the execution record's `label_overrides` map
(per-key upsert): a non-empty value sets/replaces the override for that
cluster_id, an empty string deletes it (restoring the original LLM/auto
label). Overrides are applied server-side wherever labels are read —
execution GETs (`centroids[].label`) and the cluster visualization
endpoint (`cluster_label` on centroid points) — so all clients agree.

Overrides are per-run because cluster ids (`cl_0`, `cl_1`, ...) are
assigned per-run: a rename on one execution never leaks onto another.

Example body: `{"labels": {"cl_0": "Gadget Reviews", "cl_2": ""}}`
(renames cl_0, deletes any override on cl_2).

patch/v1/clusters/{cluster_id}/executions/{run_id}/labels

Path parameters

cluster_idstring required

Cluster ID

run_idstring required

Run ID whose labels to rename

Request body

labelsobject required

Map of cluster_id -> new label (e.g. {'cl_0': 'Gadget Reviews'}). Values are trimmed; a non-empty value sets/replaces the override for that cluster_id, an empty string deletes it. Labels are capped at 200 characters. At least one entry is required.

Example request

{
  "labels": {
    "cl_0": "Gadget Reviews"
  }
}

Response

Successful Response

cluster_idstring required

Cluster the execution belongs to

run_idstring required

Execution whose labels were patched

label_overridesobject

The execution's full label_overrides map AFTER applying this patch (merged; deleted keys removed). Empty dict when the last override was just deleted.