The reference for an artifact factory.

Esy automates the production of high-quality, reviewable artifacts. The reference covers the API contract, runtime semantics, cost accounting, and the workflow templates running in production today.

API reference How Esy works

POST/v1/runsapi · v1

{
  "templateId": "generate-clip-art-asset",
  "intake": {
    "intent": {
      "prompt": "a chipmunk family in a nest",
      "style": "cartoon",
      "aspectRatio": "1:1"
    },
    "runtime": {
      "backgroundRemovalEnabled": true
    }
  }
}

201 created·42.1s runtime·$0.053 estimated

Reference atlas

The primitives that make Esy measurable.

Workflows on Esy are defined at three levels — Schema declares the rules, Template is a predesigned workflow, Specification is the per-run populated instance. Eight entries define the surface area. Read these first; everything else is a specialization.

Concepts · Workflow primitives

Workflow schemas

The platform contract every Workflow Template must satisfy. Required fields, allowed types, gate-unlock grammar, validation rules.

Read Concepts · Workflow primitives

Workflow templates

Reusable templates that satisfy the Schema. Define intake, runtime steps, providers, quality gates, and budget policy.

Read Concepts · Workflow primitives

Workflow specifications

Per-run populated instances of a Template. The deterministic blueprint production reads to build the artifact.

Read Concepts

Runs

Durable execution records with per-step telemetry, provider settings, costs, and outcomes.

Read Concepts

Artifacts

Generated outputs — visual, video, research, or knowledge — with full provenance back to their run.

Read Concepts

Costs

Estimated, provider-reported, and reconciled cost states. Every number has a documented source.

Read Reference

API

Runtime endpoints for creating runs, listing persisted outputs, and inspecting telemetry.

Read Reference

Guides

Step-by-step walkthroughs for the workflow templates running in production today.

Read

Operating principles

How Esy thinks about producing output.

Structure over prompting

Work begins with a workflow template — a structured intake designed for a specific artifact class. Not a chat box hoping for the right output.

Artifacts over conversations

Outputs are persisted with provenance, telemetry, and review state. A conversation can be the artifact; ephemeral chat history cannot.

Ready-to-use over requires-editing

Finished work, not rough drafts. Artifacts pass quality gates before they reach review or delivery.