Ideogram Concurrency and Queue Control

Overview

Keep paid image work inside a measurable concurrency envelope. Combine admission control, tenant fairness, operation deadlines, and endpoint-aware retry so a traffic burst does not become duplicate spend, an unbounded queue, or persistent 429 pressure.

Prerequisites

• Request arrival rate, latency objective, output count, endpoint mix, and cost ceiling.
• Queue ownership, per-tenant policy, cancellation behavior, and overload response.
• Current account capacity and an approved contact path for increased scale.

Current Contract

Ideogram's API overview documents a default limit of 10 in-flight requests and directs larger-capacity needs to partnership@ideogram.ai. This is a concurrency boundary, not permission to launch ten workers per process. Account-wide observed behavior remains authoritative.

Authentication

Workers inject IDEOGRAM_API_KEY server-side and send Api-Key only to https://api.ideogram.ai. Queue records and metrics must exclude keys, prompts, images, and response URLs.