{
  "fixes": {
    "slug": "openai-image-api",
    "name": "OpenAI Image API",
    "listing": "https://www.anchorterminal.com/tools/openai-image-api",
    "markdown": "# Fix list: OpenAI Image API\n\nFrom Anchor Terminal's listing at https://www.anchorterminal.com/tools/openai-image-api, the October 2026 research run, assessed 1 October 2026. Grade BB, 72.7 out of 100.\n\nThis is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.\n\nFor a coding agent working on OpenAI Image API: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.\n\n## 1. Payments \u0026 pricing, 20 out of 100, up to 10 more on the total\n\nWhy it scored 20: No x402, MPP or L402 (0). Per-token prices published without a login. No per-image figure for GPT Image 2.5, but the unit price is public (20). No free tier, prepaid credit needed (0). Human sign-up and organisation verification before the first GPT Image call (0).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):\n\nThe published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).\n\n- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.\n- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for \"contact sales\" or prices behind a login.\n- 20, a free tier or trial that doesn't need a card.\n- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).\n\nPayment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.\n\nOpen-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.\n\n## 2. Agent ergonomics, 72 out of 100, up to 4.6 more on the total\n\nWhy it scored 72: Output size is controlled with `size`, `quality`, `output_format`, `output_compression` and `n`, but images come back as base64 only, so a raw response is large (18). Output-size controls, nothing to paginate (15). Error types an agent can branch on, with moderation separated from server faults (16). No idempotency key on image endpoints, so a retried generation that had succeeded is billed again. Backoff guidance is in the rate-limit guide (8). Only `model` and `prompt` required, official Python and TypeScript SDKs among others (15).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):\n\n- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).\n- 20, pagination, filtering and output-size controls.\n- 20, actionable, documented error responses, codes and messages an agent can recover from.\n- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.\n- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.\n\nModels are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.\n\n## 3. Reliability, 80 out of 100, up to 4 more on the total\n\nWhy it scored 80: Public status page at status.openai.com with incidents filed per component (20). Three API image incidents in the last 90 days, elevated errors on 21 July (error rates back to normal after about 53 minutes, closed after 2 h 46 min), gpt-image-2 errors for 13 minutes on 24 July and gpt-image-2.5-flare errors for 40 minutes on 16 September. ChatGPT had four more image incidents that didn't touch the API. Minor only (20). Image limits published per tier, 5 to 250 images a minute on GPT Image 2.5 Flare (15). 429 handling documented with Retry-After, x-ratelimit headers and backoff code (15). The 99.9 per cent Scale Tier SLA doesn't cover image models (0). GA (10).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):\n\nHosted APIs, MCP servers, models and platforms.\n\n- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).\n- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.\n- 15, rate limits documented with numbers.\n- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.\n- 10, an SLA published for any paid tier.\n- 10, the surface agents use is generally available, not beta or preview.\n\nLocal packages, SDKs, frameworks and stdio MCP servers.\n\n- 20, installs from an official package with supported runtimes stated.\n- 25, a public CI and test suite, passing on the default branch.\n- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).\n- 15, semver discipline and breaking changes called out in a changelog.\n- 15, version 1.0 or later, or declared stable.\n\nProtocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.\n\n## 4. Security \u0026 auth, 85 out of 100, up to 2.6 more on the total\n\nWhy it scored 85: Project API keys with restricted per-endpoint permissions, service-account keys and revocation (30). Read-only key permissions, per-project model allow-lists and spend limits. No destructive actions on the image endpoints (15). Returns generated images only, no third-party content (10). Audit Logs API records key and project events, and usage is broken down per project and key, but there's no per-request log (10). security.txt valid, a public bug bounty, SOC 2 Type 2 and a trust portal (20).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-security):\n\n- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.\n- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.\n- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.\n- 0 to 15, audit logs or per-call visibility for the operator.\n- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.\n\nModels are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.\n\n## 5. Maintenance \u0026 community, 79 out of 100, up to 1.8 more on the total\n\nWhy it scored 79: GPT Image 2.5 Sunburst and Flare released on 8 September 2026, 23 days ago (30). Model churn in place of release counts. Notice for GA image models meets OpenAI's six-month policy (gpt-image-1 announced 22 April for 23 October, three more announced 2 June for 1 December), but six image models leave the API within seven months (12). Public changelog, developer forum and support (12). openai-node shipped nine releases between 26 August and 10 September, npm is at 7.25.0 (15). SDK packages current with CI (10).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):\n\n- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.\n- 20, at least three releases or dated changelog entries in the last 90 days.\n- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.\n- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).\n- 10, package health, current dependencies and CI.\n\nModels are read for deprecation notice periods and model churn rather than release counts.\n\n## 6. Schema \u0026 documentation, 90 out of 100, up to 1.6 more on the total\n\nWhy it scored 90: OpenAPI spec published in openai/openai-openapi (25). llms.txt at developers.openai.com (10). The guide says when to use Sunburst (precise edits) and when Flare (fast everyday generation), and when to use the Image API versus the Responses tool (15). Typed parameters with enums for size, quality, output_format, background and moderation, though several default to `auto` (13). Examples in every language and named error types such as `moderation_blocked` and `image_generation_user_error`, but no full error catalogue for images (12). Dated snapshots and a public changelog (15).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):\n\nAPIs and MCP servers.\n\n- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).\n- 10, llms.txt or Markdown docs served for agents.\n- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.\n- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.\n- 0 to 15, examples and documented error responses.\n- 15, versioning and a public changelog.\n\nModels are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.\n\n## 7. Transparency \u0026 trust, 92 out of 100, up to 0.7 more on the total\n\nMade of editorial 83, provenance 100.\n\nWhy it scored 92: Closed models, clear Services Agreement that assigns output to the customer (15). The data controls page gives per-endpoint retention, 30-day abuse logs, no training on API data by default and ZDR eligibility for every GPT Image model, consistent with the policies (28). Deprecation policy with notice periods by model class and a dated table (20). A subprocessor list of 18 vendors with processing locations, updated 9 July 2026, and data residency in ten regions for image endpoints (20).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):\n\n- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.\n- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).\n- 0 to 20, a deprecation policy or notices with dates.\n- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).\n\nThe other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.\n\n## Deductions\n\nEach comes off the total. A fixed and documented problem counts for less at the next check.\n\n- On 2025-11-26 OpenAI disclosed that its analytics vendor Mixpanel was breached, exposing names, emails, rough location and IDs of API platform users. No API keys, prompts or outputs. Mixpanel was removed and the incident documented (https://openai.com/index/mixpanel-incident/). -2 because it touched every API account, decayed because it's fixed and disclosed.\n\n## What we couldn't check\n\nWhat we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.\n\n- No published statement on whether a call blocked by moderation is billed.\n- The listing's lastRelease of 2026-09-22 couldn't be matched to an image change. The last image entry in the changelog is 2026-09-08.\n\n## Weaknesses\n\n- No per-image price for GPT Image 2.5, and the cost calculator doesn't cover it\n- Tier 1 accounts get 5 images a minute on GPT Image 2.5 Flare\n- Base64-only responses put the whole image in the payload\n- Six image models removed or scheduled for removal between 2026-05-12 and 2026-12-01\n- Three API image incidents in the last 90 days, the longest about 53 minutes of elevated errors\n\n## What costs an agent a turn today\n\nThe notes we give agents before they call it. Each one is a workaround an agent shouldn't need.\n\n- Pin `quality` and `size`. `auto` makes cost and latency vary per call\n- Read `usage` in the response to track image tokens, it's the only cost signal for GPT Image 2.5\n- Don't retry `moderation_blocked` or `image_generation_user_error`. Change the prompt first\n- Honour `Retry-After` on 429 and add jitter, image limits are per minute and low at tier 1\n- Move off gpt-image-1 before 2026-10-23 and off 1-mini, 1.5 and chatgpt-image-latest before 2026-12-01\n\n## What the review panel asked for\n\n- URL response option\n- Idempotency key\n- add 2.5 to the cost calculator\n- state whether moderated calls bill\n\n## When it's done\n\nSend what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `\"kind\": \"dispute\"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.\n",
    "grade": "BB",
    "score": 72.7,
    "assessed": "2026-10-01",
    "run": "October 2026 research run",
    "categories": [
      {
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "score": 20,
        "maxGain": 10,
        "reason": "No x402, MPP or L402 (0). Per-token prices published without a login. No per-image figure for GPT Image 2.5, but the unit price is public (20). No free tier, prepaid credit needed (0). Human sign-up and organisation verification before the first GPT Image call (0).",
        "checklist": [
          "The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).",
          "- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.\n- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for \"contact sales\" or prices behind a login.\n- 20, a free tier or trial that doesn't need a card.\n- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).",
          "Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.",
          "Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-payments"
      },
      {
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "score": 72,
        "maxGain": 4.6,
        "reason": "Output size is controlled with `size`, `quality`, `output_format`, `output_compression` and `n`, but images come back as base64 only, so a raw response is large (18). Output-size controls, nothing to paginate (15). Error types an agent can branch on, with moderation separated from server faults (16). No idempotency key on image endpoints, so a retried generation that had succeeded is billed again. Backoff guidance is in the rate-limit guide (8). Only `model` and `prompt` required, official Python and TypeScript SDKs among others (15).",
        "checklist": [
          "- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).\n- 20, pagination, filtering and output-size controls.\n- 20, actionable, documented error responses, codes and messages an agent can recover from.\n- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.\n- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.",
          "Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-ergonomics"
      },
      {
        "key": "reliability",
        "name": "Reliability",
        "score": 80,
        "maxGain": 4,
        "reason": "Public status page at status.openai.com with incidents filed per component (20). Three API image incidents in the last 90 days, elevated errors on 21 July (error rates back to normal after about 53 minutes, closed after 2 h 46 min), gpt-image-2 errors for 13 minutes on 24 July and gpt-image-2.5-flare errors for 40 minutes on 16 September. ChatGPT had four more image incidents that didn't touch the API. Minor only (20). Image limits published per tier, 5 to 250 images a minute on GPT Image 2.5 Flare (15). 429 handling documented with Retry-After, x-ratelimit headers and backoff code (15). The 99.9 per cent Scale Tier SLA doesn't cover image models (0). GA (10).",
        "checklist": [
          "Hosted APIs, MCP servers, models and platforms.",
          "- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).\n- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.\n- 15, rate limits documented with numbers.\n- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.\n- 10, an SLA published for any paid tier.\n- 10, the surface agents use is generally available, not beta or preview.",
          "Local packages, SDKs, frameworks and stdio MCP servers.",
          "- 20, installs from an official package with supported runtimes stated.\n- 25, a public CI and test suite, passing on the default branch.\n- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).\n- 15, semver discipline and breaking changes called out in a changelog.\n- 15, version 1.0 or later, or declared stable.",
          "Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-reliability"
      },
      {
        "key": "security",
        "name": "Security \u0026 auth",
        "score": 85,
        "maxGain": 2.6,
        "reason": "Project API keys with restricted per-endpoint permissions, service-account keys and revocation (30). Read-only key permissions, per-project model allow-lists and spend limits. No destructive actions on the image endpoints (15). Returns generated images only, no third-party content (10). Audit Logs API records key and project events, and usage is broken down per project and key, but there's no per-request log (10). security.txt valid, a public bug bounty, SOC 2 Type 2 and a trust portal (20).",
        "checklist": [
          "- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.\n- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.\n- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.\n- 0 to 15, audit logs or per-call visibility for the operator.\n- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.",
          "Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-security"
      },
      {
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "score": 79,
        "maxGain": 1.8,
        "reason": "GPT Image 2.5 Sunburst and Flare released on 8 September 2026, 23 days ago (30). Model churn in place of release counts. Notice for GA image models meets OpenAI's six-month policy (gpt-image-1 announced 22 April for 23 October, three more announced 2 June for 1 December), but six image models leave the API within seven months (12). Public changelog, developer forum and support (12). openai-node shipped nine releases between 26 August and 10 September, npm is at 7.25.0 (15). SDK packages current with CI (10).",
        "checklist": [
          "- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.\n- 20, at least three releases or dated changelog entries in the last 90 days.\n- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.\n- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).\n- 10, package health, current dependencies and CI.",
          "Models are read for deprecation notice periods and model churn rather than release counts."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-maintenance"
      },
      {
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "score": 90,
        "maxGain": 1.6,
        "reason": "OpenAPI spec published in openai/openai-openapi (25). llms.txt at developers.openai.com (10). The guide says when to use Sunburst (precise edits) and when Flare (fast everyday generation), and when to use the Image API versus the Responses tool (15). Typed parameters with enums for size, quality, output_format, background and moderation, though several default to `auto` (13). Examples in every language and named error types such as `moderation_blocked` and `image_generation_user_error`, but no full error catalogue for images (12). Dated snapshots and a public changelog (15).",
        "checklist": [
          "APIs and MCP servers.",
          "- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).\n- 10, llms.txt or Markdown docs served for agents.\n- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.\n- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.\n- 0 to 15, examples and documented error responses.\n- 15, versioning and a public changelog.",
          "Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-schema"
      },
      {
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "score": 92,
        "maxGain": 0.7,
        "reason": "Closed models, clear Services Agreement that assigns output to the customer (15). The data controls page gives per-endpoint retention, 30-day abuse logs, no training on API data by default and ZDR eligibility for every GPT Image model, consistent with the policies (28). Deprecation policy with notice periods by model class and a dated table (20). A subprocessor list of 18 vendors with processing locations, updated 9 July 2026, and data residency in ten regions for image endpoints (20).",
        "blend": "editorial 83, provenance 100",
        "checklist": [
          "- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.\n- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).\n- 0 to 20, a deprecation policy or notices with dates.\n- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).",
          "The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-transparency"
      }
    ],
    "deductions": [
      "On 2025-11-26 OpenAI disclosed that its analytics vendor Mixpanel was breached, exposing names, emails, rough location and IDs of API platform users. No API keys, prompts or outputs. Mixpanel was removed and the incident documented (https://openai.com/index/mixpanel-incident/). -2 because it touched every API account, decayed because it's fixed and disclosed."
    ],
    "unchecked": [
      "No published statement on whether a call blocked by moderation is billed.",
      "The listing's lastRelease of 2026-09-22 couldn't be matched to an image change. The last image entry in the changelog is 2026-09-08."
    ],
    "weaknesses": [
      "No per-image price for GPT Image 2.5, and the cost calculator doesn't cover it",
      "Tier 1 accounts get 5 images a minute on GPT Image 2.5 Flare",
      "Base64-only responses put the whole image in the payload",
      "Six image models removed or scheduled for removal between 2026-05-12 and 2026-12-01",
      "Three API image incidents in the last 90 days, the longest about 53 minutes of elevated errors"
    ],
    "agentNotes": [
      "Pin `quality` and `size`. `auto` makes cost and latency vary per call",
      "Read `usage` in the response to track image tokens, it's the only cost signal for GPT Image 2.5",
      "Don't retry `moderation_blocked` or `image_generation_user_error`. Change the prompt first",
      "Honour `Retry-After` on 429 and add jitter, image limits are per minute and low at tier 1",
      "Move off gpt-image-1 before 2026-10-23 and off 1-mini, 1.5 and chatgpt-image-latest before 2026-12-01"
    ],
    "requests": [
      {
        "text": "URL response option",
        "reviews": 1
      },
      {
        "text": "Idempotency key",
        "reviews": 1
      },
      {
        "text": "add 2.5 to the cost calculator",
        "reviews": 1
      },
      {
        "text": "state whether moderated calls bill",
        "reviews": 1
      }
    ],
    "recheck": "https://www.anchorterminal.com/builders/#disputes"
  },
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-04",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.3",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  }
}