Skip to main content
DreamLayer currently exposes individual executions, not a native batch submission endpoint. A conversation is a sequence of turns, not a batch. Keep each image’s request, key, execution ID, and output separate.

A queue you can resume

Create one request JSON per image using the runnable examples. For edits, upload each reference once and store its input asset ID in that file. Use the Python queue below with agent_client.py in the same directory:
The serial queue is deliberately conservative. If you add concurrency, use a semaphore with at most two active executions across your account and one shared request limiter. Keep work queued locally when the account is busy. Bound retry attempts and honor limits.

Recover partial failures

A retryable HTTP error is not proof that a job failed. Keep uncertainty separate from terminal failure. Never rerun an entire group with fresh keys because one item failed.