API · Images

AI Image Generation API for Production Workflows

Generate and edit images through one workflow API. Change models, chain steps, and return CDN-ready outputs without rebuilding your integration.

Create an API key Read the docs

Built for agents and applications

Text-to-image and reference-image workflows

Generation, editing, upscaling, and background steps

Multiple image models behind one workflow contract

CDN-hosted outputs ready for downstream agents

server.ts

const response = await fetch(
  "https://api.imageat.com/v1/workflows/wf_image_production/runs",
  {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.IMAGEAT_API_KEY}`,
      "Content-Type": "application/json",
      "Idempotency-Key": crypto.randomUUID()
    },
    body: JSON.stringify({
      // Uses the nodes and edges saved in the published workflow.
      nodes: [],
      edges: []
    })
  }
)

const run = await response.json()
// Poll GET /v1/runs/{run_id} or subscribe with SSE.
console.log(run.run_id)

Hosted LLM API

Build with Qwen 3.8 27B Uncensored

Try long-context chat and reasoning in the imageat playground, then integrate the same model through an OpenAI-compatible endpoint.

View Qwen API pricing and playground

How it works

From instruction to production asset.

Build and publish a workflow

Choose the model, inputs, edit steps, and output once in imageat's visual workflow builder.

Create an API key

Generate a server-side iat_live_ key and keep it outside browser code and source control.

Run, observe, and receive outputs

Start runs with idempotency, follow progress by polling or SSE, and store the returned CDN URLs.

Frequently asked questions

Is this a direct model API?

imageat provides one API layer over image generation and editing workflows. You can change the model or add processing steps without rebuilding the calling application.

How is usage billed?

Runs use the credits on the imageat account connected to the API key or MCP session. The required credits depend on the selected model and workflow.

Can I use outputs commercially?

Commercial use depends on imageat's terms and the terms of the models and source assets used in your workflow.

Build once. Call it from anywhere.

Start with the hosted interface, then move the same visual workflow into your agent or production application.

Create an API key

API · Images

AI Image Generation API for Production Workflows

Generate and edit images through one workflow API. Change models, chain steps, and return CDN-ready outputs without rebuilding your integration.

Create an API key Read the docs

Built for agents and applications

Text-to-image and reference-image workflows

Generation, editing, upscaling, and background steps

Multiple image models behind one workflow contract

CDN-hosted outputs ready for downstream agents

server.ts

const response = await fetch(
  "https://api.imageat.com/v1/workflows/wf_image_production/runs",
  {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.IMAGEAT_API_KEY}`,
      "Content-Type": "application/json",
      "Idempotency-Key": crypto.randomUUID()
    },
    body: JSON.stringify({
      // Uses the nodes and edges saved in the published workflow.
      nodes: [],
      edges: []
    })
  }
)

const run = await response.json()
// Poll GET /v1/runs/{run_id} or subscribe with SSE.
console.log(run.run_id)

Hosted LLM API

Build with Qwen 3.8 27B Uncensored

Try long-context chat and reasoning in the imageat playground, then integrate the same model through an OpenAI-compatible endpoint.

View Qwen API pricing and playground

How it works

From instruction to production asset.

Build and publish a workflow

Choose the model, inputs, edit steps, and output once in imageat's visual workflow builder.

Create an API key

Generate a server-side iat_live_ key and keep it outside browser code and source control.

Run, observe, and receive outputs

Start runs with idempotency, follow progress by polling or SSE, and store the returned CDN URLs.

Frequently asked questions

Is this a direct model API?

imageat provides one API layer over image generation and editing workflows. You can change the model or add processing steps without rebuilding the calling application.

How is usage billed?

Runs use the credits on the imageat account connected to the API key or MCP session. The required credits depend on the selected model and workflow.

Can I use outputs commercially?

Commercial use depends on imageat's terms and the terms of the models and source assets used in your workflow.

Build once. Call it from anywhere.

Start with the hosted interface, then move the same visual workflow into your agent or production application.

Create an API key