civitai-orchestration

Run the client with the user command followed by the Civitai user ID, for example node civitai-client.js user 12345. This uses the manager endpoint and requires an API token with Manager role. You can add options like --take, --tag, and --excludeFailed to filter results.

Use the job command with the job ID to fetch detailed job information. The output includes the lastEvent context containing scan fields such as hive_csam_score, hive_vlm_summary, blocked_reason, and nsfwLevel, plus prompt classification flags.

The API requires a bearer token set as the CIVITAI_API_TOKEN environment variable, stored in the skill's .env file. Querying other users' workflows requires a token with Manager role; the consumer endpoints only return your own workflows.

The API does not support filtering by an exact status value. It only offers an excludeFailed boolean to remove failed, canceled, and expired workflows. To isolate a specific status, retrieve workflows and filter client-side, or use tags and metadata when creating workflows.

Use the results command with the workflow ID and the --download flag, optionally specifying --dir for the output directory. The client iterates through workflow steps, finds output blobs, and downloads each file with an inferred extension such as .png, .webp, or .mp4.

A 401 means the CIVITAI_API_TOKEN is invalid or expired, so verify the token in the .env file. A 429 indicates rate limiting, so wait before retrying. A 404 means the workflow or job ID does not exist, and 422 indicates invalid request parameters.