Ideogram Production Migration

Overview

Modernize a complete Ideogram image workflow without assuming endpoint names imply equivalent semantics. Inventory legacy and V3 behavior, select V4, P-Image, or outcome-focused tools by requirement, compare safe durable results, and preserve in-flight state and rollback.

Prerequisites

• Source routes, payloads, traffic, consumers, stored assets, async state, quality rubric, and owners.
• Target use cases, model-control needs, latency, safety, rights, cost, and retention constraints.
• Feature flags, shadow destination, reconciliation plan, canary budget, and rollback window.

Current Contract

First-party navigation labels /generate, /edit, /remix, /reframe, and /describe as Legacy Endpoints. Current surfaces include V3, V4 sync/async/transparent, P-Image, edit, remix, structured describe, magic prompt, outcome-focused tools, and custom training. Payload and rendering semantics differ.

Authentication

Preserve the server-side Api-Key boundary and environment isolation throughout migration. Dual-run fixtures and receipts must exclude keys, prompts, uploaded images, generated assets, and temporary URLs.