Skip to content
AAA.win
EN
EnglishEN中文ZH日本語JAEspañolES
SearchSubmit a tool
Menu

change record

OpenAI's GPT-4.1 API announcement: an evaluation record

A dated summary of OpenAI's April 2025 GPT-4.1 API announcement, preserved for change tracking rather than presented as current buying advice.

Event date:

Editorially reviewedVerified 2026-08-112 official or primary sources

The durable lesson is to record the exact model and product surface, because a family name and a chat product are not interchangeable test conditions.

On April 14, 2025, OpenAI announced GPT-4.1, GPT-4.1 mini, and GPT-4.1 nano in its API. The official announcement described the release in terms of coding, instruction following, and long-context use cases.

This page is a historical change record. It does not claim that the announced models, prices, limits, or availability remain unchanged. Anyone making a current purchasing or implementation decision should check OpenAI's live model and pricing documentation.

For reproducible evaluation, preserve the exact model identifier, date, endpoint or product surface, tools, prompt, and acceptance checks. A later result using a product label alone cannot be compared cleanly with this release event.

What changed

  • OpenAI announced a three-model GPT-4.1 family for API use.
  • The announcement positioned coding, instruction following, and long-context work as focus areas.
  • The release created a new model-version boundary for teams maintaining evaluation histories.

What to do now

  • Check current OpenAI documentation before assuming the 2025 availability or terms still apply.
  • Store full model identifiers and test dates in every benchmark run.
  • Retest representative tasks when a production workflow changes models.

Sources checked

Open the original pages before relying on a time-sensitive product decision.

  1. Introducing GPT-4.1 in the APIOpenAI
  2. OpenAI models documentationOpenAI
Version · v4.3.4-indexnow-root-proof

Latest releases

IndexNow root-proof request compatibility

After v4.3.3, the exact root-level {key}.txt proof returned HTTP 200, but a full request carrying keyLocation still returned HTTP 403; a minimal homepage request with the same production key and no keyLocation returned HTTP 202. This release omits that field, while the automatic full run and idempotent rerun remain deployment checks.

IndexNow key-proof compatibility

Changed IndexNow verification to the official root-level {key}.txt convention after the first production notification returned HTTP 403; revalidation remains pending, while the website, sitemaps, and Bing sitemap processing are unaffected.

Bing sitemap discovery and IndexNow change notifications

Prepared canonical sitemap discovery for Bing and added automatic IndexNow change notifications while keeping segmented sitemaps authoritative and making no claim that a notified URL has been crawled or indexed.

View all releases