Run Generation
Start an AI generation run for the attribute.
mode says what the run does: fill generates values only for assets not
generated yet (or whose last run failed); overwrite regenerates every
asset’s value, replacing the AI’s answers. Values entered by hand are kept
unless replace_manual is true, and count leaves them out accordingly;
an overwrite dry run also reports how many there are (manually_entered).
target says which assets it covers: watch = every asset in the attribute’s watch folders;
directories = assets in the given directories (recursive: true includes
their subdirectories); assets = only the listed assets, wherever they are.
Requires edit-metadata access on the project for watch, on every listed
directory or asset otherwise. An attribute without generation attached has
nothing to run and is rejected with 409 once the target is validated.
POST /metadata/attributes/{attribute_id}/generation/run is the deprecated
form of this route.
Authorizations
Aspect API key (sk_...) in Authorization header. 'Bearer ' optional.
Path Parameters
Attribute ID
Query Parameters
Return the counts without starting the run; not supported when target.kind is assets
Body
API request schema for a run: what it does and which assets it covers.
fill runs only the assets not run yet (or whose last run failed); overwrite re-runs every asset, replacing the AI's answers; answers entered by hand are kept unless replace_manual is true
fill, overwrite Every asset the column watches; rejected when it watches nothing.
- WatchRunTarget
- DirectoriesRunTarget
- AssetsRunTarget
With overwrite, also replace answers entered by hand. Ignored by fill
Response
Successful Response
API response schema for an explicit run's counts.