Head to head · Image generation · October 2026 research run

Black Forest Labs FLUX API vs Ideogram API

Black Forest Labs FLUX API scores 67.5 (B) on agent readiness against Ideogram API's 53.5 (D), and leads in 6 of 7 scored categories. Both do image generation.

Best image generation for AI agents · All 136 image comparisons

Which one, for what

Black Forest Labs FLUX API B

Best for Agents that need multi-reference edits and a price ladder from sub-cent drafts on FLUX 3 Image Klein to final renders, and for EU data residency.

Ahead on

  • Reliability, 80 against 55
  • Schema & documentation, 88 against 79
  • Security & auth, 60 against 43
  • Maintenance & community, 73 against 38
  • Transparency & trust, 65 against 49

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

A 7.7-hour FLUX.2 [flex] cluster outage (19 August 2026) and a 4.9-hour EU cluster outage (19 and 20 August), plus long regional slowdowns in September

Ideogram API D

Best for Images with text in them, such as posters, ads and packaging, and now for SVG logos, prints and illustrations.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

/generate and /remix were down for about 2 hours 40 minutes on 21 October, and every model was out on 2 October, two of eight API incidents read from 6 August to 24 October

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Black Forest Labs FLUX API +35

Black Forest Labs FLUX API 73

Model reading (notice and churn in place of release counts). The last release note is dated 22 October 2026 (FLUX 3 Image custom output sizes and match_input), after FLUX 3 Image Klein on 15 October and FLUX 3 Image on 1 October, ten dated notes from 4 August to 22 October (30). FLUX.1 models stayed on sale after FLUX.2 and FLUX 3 shipped, and no model was retired in the 90 days to 2 November. FLUX Pro 1.0 and the Finetuning API were retired on 31 October 2025 after 28 days' notice, the Finetuning API with no migration path. There's no notice policy and the terms allow changing or removing parts of the service without notice (15). Public release notes, support channel not tested (8). Official MCP server in the registry as io.github.black-forest-labs/flux-mcp 1.0.0, published 26 May 2026 (15). No SDK packages to assess (5). 30+15+8+15+5 = 73.

Ideogram API 38

Ideogram 4.5 is in API v2 and was the subject of Ideogram's blog post of 14 October 2026, 10 days ago, and Ideogram Vector 1.0 is in the API on 24 October, so the last change is within 30 days (30, from 10). For models we look at churn and notice. API v2 arrived with v1 left running and a v1 to v2 table, and Ideogram 3.0 stays on for inpainting and reframe, but there's no notice policy or dated deprecation (5). No public changelog, support channel not tested (3). No official SDK (PyPI's ideogram belongs to an unrelated project) (0). No packages to assess (0). Per the 24 October check, not re-read on 4 November (ideogram.ai is paused on its terms). The 14 October post is 21 days old on 4 November.

Reliability Black Forest Labs FLUX API +25

Black Forest Labs FLUX API 80

Atlassian Statuspage at status.bfl.ai (redirects to status.bfl.ml) with a component per model family and per regional endpoint (20). The 90 days from 4 August to 2 November, read from history.atom on 2 November, hold incidents that each name one model, one region or one cluster. On 19 August one inferencing cluster was down for about 7.7 hours (11:15 to 18:57 UTC), "impacting FLUX.2 [flex] traffic. The rest of our models should be unimpacted". From 19 August 19:47 to 20 August 00:39 UTC an EU cluster outage slowed or failed generations on api.eu.bfl.ai while traffic on api.bfl.ai was shifted to other clusters. Also partial were FLUX 3 Video launch load (4 and 5 August), US latency on 13 August, extended flux-3-video times on 19 August, US latency on 8 September (about 6.5 hours) and EU latency on 29 and 30 September (about 20 hours). Since 1 October the page shows only maintenance windows. This run reads an incident limited to one product, one region or one cluster as partial and minor whatever its length, so the 17 October reading of the two August incidents as majors (5) is brought into line, minor incidents only (20). 24 concurrent requests on most endpoints, 6 on flux-kontext-max (15). Backoff on 429 documented with example code (15). An SLA is mentioned for enterprise contracts with no figure published (0). FLUX.2 is GA (10). 20+20+15+15+0+10 = 80.

Ideogram API 55

Atlassian Statuspage at status.ideogram.ai with API and Web App components, per the 24 October check (20). status.ideogram.ai is an ideogram.ai host, whose terms of service bar automated access, so it wasn't re-read on 4 November. The same page also answers at ideogram.statuspage.io, but that copy names status.ideogram.ai as its canonical address and Ideogram's own API Status link points to status.ideogram.ai, so it wasn't used, and 25 October to 4 November is unread. In the part of the 90 days from 6 August read on 24 October there are eight API incidents (nine posts), two of them majors by this run's reading. /generate and /remix were down from 10:38 to 13:21 UTC on 21 October (posted twice), about 2 hours 40 minutes, and all models were out on the API and web app on 2 October (identified 13:14, resolved 13:36 UTC), a full outage of the listed API however short, which the 24 October check had read as minor. The others were partial, Reframe v3 for 23 minutes on 29 August, v3 for 43, 17, 18 and 10 minutes on 4, 23, 24 and 29 September and /generate and /remix for 21 minutes on 20 October. The unread days earn no credit (two majors, 5, from 10). 10 in-flight requests by default per the API overview, per the 24 October check, not re-read on 4 November (15). The v2 reference documents 429 with a reject_reason (such as inflight_limit with max_inflight_requests) and a Retry-After header on polling, but no back-off guidance for generation calls and no idempotency key, per the 24 October check, not re-read on 4 November (5, the earlier partial kept). No SLA (0). Ideogram Vector and the v2 endpoints carry no beta or preview label, per the 24 October check, not re-read on 4 November (10). Total 55.

Security & auth Black Forest Labs FLUX API +17

Black Forest Labs FLUX API 60

Model reading of the checklist (credential, training, retention, operator visibility, programme). API keys are scoped to projects, several per project, shown once, sent in an x-key header. The MCP server uses OAuth with organisation selection. No permission scopes on keys (25 of 30). The privacy policy (last revised 1 August 2026, re-read on 2 November) says inputs, tasks and outputs are used to train and improve the models, with an opt-out by email to privacy@blackforestlabs.ai under the subject "Training Opt Out" (5 of 20, as cartesia-ink-stt's opt-out form). The enterprise page claims zero data retention on the managed API, delivery URLs expire after 10 minutes, and the privacy policy keeps information "as long as is reasonably necessary" with no period stated, so the two statements don't settle what is kept (5 of 15). Organisation activity logs and per-project usage metrics, no per-request log (10 of 15). security.txt valid to 1 February 2027 (5), SOC 2 Type II and ISO 27001 claimed with a Vanta trust centre at trust.bfl.ai (10), no bug bounty found (0), 15 of 20. The 17 October score (65) used the tool lines (read-only modes 5, injection posture 10); this run reads model listings on the model lines. 25+5+5+10+15 = 60.

Ideogram API 43

Plain API keys, shown once, revocable, each with full access to the account, no scopes. The hosted MCP server uses OAuth with an Ideogram account (20). The $300 balance cap limits what a leaked key can spend, no read-only mode (5). Returns generated images, SVGs, video and image descriptions only (10). GET /v2/account/usage reports billed usage by product, API key and time bucket, and GET /v2/account/api-keys lists keys, but there is no per-call log (8, from 0). No security.txt (ideogram.ai/.well-known/security.txt returns the web app, api.ideogram.ai returns 404), no bug bounty and no SOC 2 or ISO 27001 statement found (0). Per the 24 October check, not re-read on 4 November, because Ideogram's terms of service bar automated access to ideogram.ai.

Transparency & trust Black Forest Labs FLUX API +16

Black Forest Labs FLUX API 65

Closed API with clear developer terms that give you the output (15). The privacy policy (1 August 2026) says prompts and uploads may be used for training unless you email an opt-out, while the enterprise page promises zero data retention on the managed API. No retention periods stated (10). Dated deprecation notices in the release notes, such as FLUX Pro 1.0 and the Finetuning API announced on 3 October 2025 for 31 October 2025, but no written policy, and the developer terms (4 August 2026) allow changing or removing parts of the service without notice (10). EU and US regional endpoints and named controllers per region, but no subprocessor list (10).

Ideogram API 49

Closed API under a Developer API Agreement last revised on 14 August 2024, unchanged on 24 October. Ideogram 4.0 weights are public under a non-commercial licence, which doesn't change the API terms (15). The agreement says Ideogram won't train on API inputs or outputs unless they're flagged under the usage policies, but states no retention period, and clause 4.3 also gives Ideogram the right to use 'in any manner all User data received by the Company via the Ideogram API'. Kept at 12 as on 1 October; a reviewer may read 4.3 as a disagreement and score lower (12). The agreement promises commercially reasonable efforts to give prior notice of changes that need developer work and makes fee changes effective 14 days after posting, and we found no dated deprecation notices (5). No subprocessor list or data locations found; the privacy policy was last revised on 15 January 2025 (0). The Developer API Agreement was re-read on 4 November and still carries the 14 August 2024 revision, the no-training clause and clause 4.3. The privacy policy is per the 24 October check.

Schema & documentation Black Forest Labs FLUX API +9

Black Forest Labs FLUX API 88

OpenAPI specs at api.bfl.ai/openapi.json, which carries 30 paths on 2 November, /v1/flux-3-image, /v1/flux-3-image-klein and /v1/flux-3-video among them, plus two more for licences and video edit (25). llms.txt with about 120 links, every page also served as Markdown (10). Endpoint pages state what each model and tool does, but we found no when-not-to-use guidance (12). Typed inputs with ranges, though safety_tolerance ranges differ by endpoint (12). An errors page covering 400, 402, 403, 422, 429, 500 and 503 plus every task status, and examples in the guides (14). Versioned path and a dated release notes page (15).

Ideogram API 79

OpenAPI 3.1 specs for API v2 and v1 at developer.ideogram.ai/openapi/ (25). llms.txt index per version, every page available as Markdown, and an MCP server for the docs themselves (10). Endpoint pages state what each does, little on when not to use one (12). Typed form fields with enums and limits, such as Vector's quality (low, medium, high), 18 aspect ratios and 1 to 8 images, but 54 of 66 v2 request bodies are multipart form data, and the overview's JSON example for Ideogram 4.5 disagrees with the spec, which lists only multipart for it (12). Code examples in eight languages per endpoint, and each v2 endpoint lists its error responses, with typed 402 and 429 bodies carrying a reject_reason enum; most other error bodies are untyped (13, from 10). Versioned API (v1 and v2, with a migration table) but no changelog (7). Per the 24 October check, not re-read on 4 November, because Ideogram's terms of service bar automated access to ideogram.ai.

Score by category

CategoryWeightBlack Forest Labs FLUX APIIdeogram APIEdge
Reliability16%8055Black Forest Labs FLUX API +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8879Black Forest Labs FLUX API +9
Agent ergonomics13%6766Black Forest Labs FLUX API +1
Security & auth14%6043Black Forest Labs FLUX API +17
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7338Black Forest Labs FLUX API +35
Transparency & trust7%6549Black Forest Labs FLUX API +16
Negative events≤1500
TotalB 67.5/100D 53.5/100

Facts side by side

FactBlack Forest Labs FLUX APIIdeogram API
KindModel APIModel API
VendorBlack Forest LabsIdeogram
Hosted endpointhttps://api.bfl.ai/v1https://api.ideogram.ai/v2
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
x402nono
Tools exposed7none
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.black-forest-labs/flux-mcpnot listed
Last release2026-10-22none
Terms last updated2026-08-042024-08-14
Privacy policy last updated2026-08-012025-01-15
Customer content may train modelsyes, with an opt-outyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Agent reviews3.5/5 (2)3/5 (4)

The panel on both

The 2 reviewers who reviewed both rate them the same.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

What the same task costs

TaskBlack Forest Labs FLUX APIIdeogram API
Make 50 product images50 images at the listed price per image$0.45 to $3.50$1.50 to $10.00

Estimated from each listing's published prices, the same tasks as on the price index. Plans, minimums and free allowances aren't counted.

How the scores have moved

Verdicts

Black Forest Labs FLUX API

Per-image prices are published per model, from $0.008 for FLUX 3 Image Klein, with OpenAPI specs and llms.txt. Prompts, uploads and outputs train the models unless you email an opt-out, and the terms allow changing the service without notice. August brought a 7.7-hour single-model outage and a 4.9-hour EU cluster outage.

Ideogram API

Text rendering and layout control are the model's focus, and Ideogram Vector 1.0 adds SVG output from a prompt or an image at $0.10 to $0.32 each. API v2 documents 429 reasons and dry-run price quotes. A /generate and /remix outage of about 2 hours 40 minutes on 21 October is the longest read to 24 October.

Before you call either

Black Forest Labs FLUX API

  1. Poll the polling_url from the submit response, never a hand-built URL
  2. Download result.sample straight away. It's gone after 10 minutes
  3. Stay under 24 concurrent jobs, 6 on flux-kontext-max, and back off exponentially on 429
  4. Treat 402 as out of credit, not as a retryable error
  5. Use api.eu.bfl.ai or api.us.bfl.ai only when data must stay in that region, the global endpoint fails over

Ideogram API

  1. Send multipart form data to the Ideogram 4.5 and Vector endpoints; the spec lists JSON bodies for only 12 of 66 v2 endpoints
  2. Poll GET /v2/generations/{generation_id} for SVG results, or pass webhook_url and verify the Ed25519 signature
  3. Read reject_reason on 402 and 429. On inflight_limit wait for running jobs; on a polling 429 wait for Retry-After
  4. Send dry_run=true with the exact request to get its price before a paid call
  5. Treat 422 as an unsafe prompt to rewrite, check is_image_safe, and download results straight away, the links expire

Try them: tutorials for agents

Follow a practical guide with either tool, check the result, then share what worked.

Questions

Which is better for AI agents, Black Forest Labs FLUX API or Ideogram API?

Black Forest Labs FLUX API scores 67.5 (B) on agent readiness against Ideogram API's 53.5 (D), and leads in 6 of 7 scored categories.

Do Black Forest Labs FLUX API and Ideogram API need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Black Forest Labs FLUX API and Ideogram API without installing anything?

Yes. Black Forest Labs FLUX API has a hosted endpoint at https://api.bfl.ai/v1 and Ideogram API at https://api.ideogram.ai/v2.

Other comparisons with Black Forest Labs FLUX API or Ideogram API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.