Published boundary

Exact coverage, including when it is incomplete.

Direct APIs only · official sources only · reviewed changes only

AI-Buzz monitors a deliberately small source set. A required source that is failed, stale, changed but unreviewed, conflicting, or unevaluated blocks a complete status. Unsupported identifiers stay visible as unsupported; they never appear monitored.

Supported now

Three direct provider APIs

Checked hourly · stale after four hours

OpenAI direct API

OpenAI

Direct OpenAI model and API lifecycle notices.

Required sources

OpenAI API deprecations (opens in a new tab)
Dated model and API deprecations and shutdowns.
OpenAI API changelog (opens in a new tab)
Explicit API and behavior changes.

Anthropic direct API

Anthropic

Direct Claude model and Messages API lifecycle notices.

Required sources

Claude model deprecations (opens in a new tab)
Claude model deprecations, retirements, and replacements.
Claude Platform release notes (opens in a new tab)
Explicit Claude API and behavior changes.

Gemini API

Google

Google AI Studio Gemini model and API lifecycle notices.

Required sources

Gemini API deprecations (opens in a new tab)
Gemini model shutdowns and replacement dates.
Gemini API release notes (opens in a new tab)
Gemini API changes and dated migrations.

Included

Material lifecycle and compatibility changes

Deprecation or retirement
Dated migration or changed deadline
Explicit breaking request or response change
Explicit endpoint, schema, or authentication change
Correction or withdrawal of a published change

Not monitored

Broad changes that do not define this product

Pricing, incidents, launches, policy, or terms updates
SDK and package releases
Indirect platforms such as Bedrock, Vertex AI, Azure AI, or OpenRouter
Arbitrary webpages, repository scanning, and custom sources

Fail-closed status

Silence is useful only when coverage is known.

“No reviewed known lifecycle change” is a timestamped finding inside the supported source boundary. It is not a claim that an application is safe or that no other change exists.

“Caught up” additionally requires that every required source is healthy and current and that the user has viewed every current matching published version. A future deadline can still require action while the report is caught up.

Check your exact dependencies against this boundary.

Add identifiers manually. Unsupported dependencies stay clearly unsupported.