Ideogram Cost Governance

Overview

Control prepaid Ideogram consumption without embedding prices that can drift. Tie admission to an accountable budget, choose the narrowest route, bound outputs and retries, and measure durable safe results rather than HTTP success or generated candidates.

Prerequisites

• Team billing owner, current balance source, budget period, workload owner, and quality floor.
• Request volume, endpoint and rendering mix, output count, retry rate, unsafe rate, and storage failures.
• A current pricing review from the first-party API pricing page.

Current Contract

Ideogram API billing is separate from the web application, requires positive prepaid credit, and can use auto-recharge. Keys in one team share credits and billing, so per-key usage is not a separate vendor balance. Prices and recharge choices are time-sensitive and must be verified rather than copied into this skill.

Authentication

Workers use server-side IDEOGRAM_API_KEY as Api-Key to https://api.ideogram.ai. Cost evidence may include team, endpoint, request, and opaque generation identifiers, but not the key, prompts, images, or URLs.