Concepts · Artifacts

Artifacts

Artifacts are the durable outputs produced by workflow runs — visual, video, research, or knowledge. Every artifact carries provenance back to the workflow and run that produced it.

Artifact classes

Class	Content
`visual`	Images: clip art, illustrations, coloring pages, covers.
`video`	Short-form video: scenes, stitched films, animations.
`research`	Structured research outputs and screenplays.
`knowledge`	Project state, decisions, and reusable context records.

Provenance

Every artifact references the runId and templateId that produced it, so you can trace prompt, provider, model, timing, cost, and review state from any persisted output through GET /v1/runs/{runId}.

GET /v1/artifacts/artifact-0dc32dbbjson

{
  "id": "artifact-0dc32dbb",
  "runId": "run-a1b2c3d4",
  "templateId": "generate-clip-art-asset",
  "artifactClass": "visual",
  "status": "review",
  "content": {
    "type": "image",
    "url": "https://images.esy.com/artifacts/clip-art/artifact-0dc32dbb/processed.webp",
    "storageKey": "artifacts/clip-art/artifact-0dc32dbb/processed.webp",
    "mimeType": "image/webp",
    "width": 1024,
    "height": 1024
  },
  "createdAt": "2026-05-16T22:14:43.711Z"
}

Status values

Status	Meaning
`review`	Produced and persisted; awaiting operator review.
`approved`	Reviewed and accepted as the canonical output.
`rejected`	Reviewed and discarded. Record kept for provenance.
`draft`	Intermediate output, not yet user-visible.

Visual artifacts

A visual artifact has two files: raw (model output) and processed (post background removal and any QA passes). Both are stored as WebP. The artifact response includes the public url for the processed file; the storageKey is stable and safe to persist on your side.

visual file pathspath

artifacts/{artifactType}/{artifactId}/raw.webp
artifacts/{artifactType}/{artifactId}/processed.webp

Video, research, and knowledge artifacts have their own content shapes; those will be documented here as each class ships its public contract.