Curate a dataset item from a generation
POST/v1/projects/:project_id/datasets/:dataset_id/items/from-generation
Promotes a real, completed generation into a test case: its input messages become the item's input, and its own answer becomes expected_output unless you supply one. Use it to build an evaluation set out of production traffic rather than hand-authoring fixtures.
The item is a copy, not a view. It keeps working after the source generation's content is purged, and source_generation_id goes null if that generation is deleted — a purge can never quietly stop a suite from being runnable.
Requires both evaluations:CreateDataset and generations:GetGeneration: the call copies content out of a generation, so a principal that may not read that generation may not curate it either.
Only a completed generation can be promoted (409 GENERATION_NOT_COMPLETED), and only while its content is still available: an agent or project running with trace_content_mode: none never stored the input, and a purged or expired generation no longer has it (409 GENERATION_CONTENT_UNAVAILABLE). Generations that predate input recording answer the same way.
Request
Responses
- 201
- 400
- 401
- 403
- 404
- 409
- 413
- 429
- 500
- 502
- 4XX
Dataset item created from the generation
Bad request (generation_id missing, or the generation belongs to a different project than the dataset)
Unauthorized
Forbidden
Dataset or generation not found
The generation has not completed, its content was never stored or has been purged, or the project's storage_bytes quota is exceeded (QUOTA_STORAGE_EXCEEDED; delete stored content or raise the quota — no Retry-After is sent, since no window reset clears a stored total)
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there