qwen3.8-flash · API launch · Frankfurt, Germany · EU
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Browse releases, API launches, weight publications and lifecycle changes by year or date, with links to model families, versions and official announcements.
2026·372records
372 records in this range. Releases, API launches, open-weight releases and lifecycle events are grouped by month, with a separate chart for each year.
No records in this date range. Adjust the dates or choose a year above.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Model release date from the official announcement.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-terra. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-terra. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-luna. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-image-2.5-sunburst, gpt-image-2.5-flare. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
The preview API has officially closed. The provider recommends gemini-omni-1.1-flash; check Enterprise GA interfaces separately. Our retrieval date is not treated as an announcement or release date.
The preview API has officially closed. The provider recommends gemini-omni-1.1-flash; check Enterprise GA interfaces separately. Our retrieval date is not treated as an announcement or release date.
The preview API has officially closed. The provider recommends gemini-omni-1.1-flash; check Enterprise GA interfaces separately. Our retrieval date is not treated as an announcement or release date.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date is when the announced service change takes effect, rather than our observation date. API lifecycle and weight terms remain separate.
The date is when the announced service change takes effect, rather than our observation date. API lifecycle and weight terms remain separate.
The date is when the announced service change takes effect, rather than our observation date. API lifecycle and weight terms remain separate.
The date is when the announced service change takes effect, rather than our observation date. API lifecycle and weight terms remain separate.
Model release date from the official announcement.
The official announcement date, rather than the first API launch or weight upload.
Official retirement date: 2027-01-14. Suggested replacement IDs: gpt-6-luna. No paid API probes were run.
Official retirement date: 2027-01-14. Suggested replacement IDs: gpt-6-luna. No paid API probes were run.
Official retirement date: 2027-01-14. Suggested replacement IDs: gpt-6-luna. No paid API probes were run.
Official retirement date: 2027-01-14. Suggested replacement IDs: gpt-6-luna. No paid API probes were run.
Model release date from the official announcement.
This version is generally available.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The release date is stated on the official model page. It is separate from API ID suffixes and knowledge cutoffs.
This version is generally available.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Nova 2.5 Sonic became available through the Amazon Bedrock API.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The old API ID routes to grok-voice-transcribe-2.0. Retirement and initial release dates are recorded separately.
Official retirement date: 2027-01-06. Suggested replacement IDs: gpt-realtime-2.1-mini. No paid API probes were run.
Official retirement date: 2027-04-01. Suggested replacement IDs: gpt-6-luna. No paid API probes were run.
Official retirement date: 2027-04-01. Suggested replacement IDs: gpt-6-sol. No paid API probes were run.
Official retirement date: 2027-01-06. Suggested replacement IDs: gpt-realtime-2.1-mini. No paid API probes were run.
Official retirement date: 2027-04-01. Suggested replacement IDs: gpt-6-sol. No paid API probes were run.
Official retirement date: 2027-01-06. Suggested replacement IDs: gpt-realtime-2.1-mini. No paid API probes were run.
New Decisions API models: pplx-decider-v1.1-27b.
New Decisions API models: pplx-decider-v1.2, pplx-decider-flash-v1.2.
New Decisions API models: pplx-decider-v1-27b.
The earlier decision model has been superseded. Its API ID routes to v1.2; the exact transition date is unknown.
The earlier decision model has been superseded. Its API ID routes to v1.2; the exact transition date is unknown.
amazon.nova-canvas-v1:0 is no longer available on Amazon Bedrock.
amazon.nova-reel-v1:0 is no longer available on Amazon Bedrock.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Model release date from the official announcement.
The release date is stated on the official model page. It is separate from API ID suffixes and knowledge cutoffs.
The legacy product API is no longer supported. Synchronous and streaming calls are progressively rewritten as Agent requests; asynchronous calls stop. This does not retire the current Agent Sonar models.
The release date is stated on the official model page. It is separate from API ID suffixes and knowledge cutoffs.
This version is generally available.
This version is generally available.
Model release date from the official announcement.
Model release date from the official announcement.
Model release date from the official announcement.
Model release date from the official announcement.
This version is generally available.
This version is generally available.
The official announcement date, rather than the first API launch or weight upload.
This version is generally available.
This version is generally available.
Model release date from the official announcement.
This version is generally available.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The release date is stated on the official model page. It is separate from API ID suffixes and knowledge cutoffs.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
This version is generally available.
Official retirement date: 2027-02-26. Suggested replacement IDs: gpt-live-transcribe, gpt-transcribe. No paid API probes were run.
Official retirement date: 2027-02-26. Suggested replacement IDs: gpt-live-transcribe, gpt-transcribe. No paid API probes were run.
Official retirement date: 2027-02-26. Suggested replacement IDs: gpt-live-transcribe, gpt-transcribe. No paid API probes were run.
Official retirement date: 2027-02-26. Suggested replacement IDs: gpt-live-transcribe, gpt-transcribe. No paid API probes were run.
This version is generally available.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Model release date from the official announcement.
The date is when the announced service change takes effect, rather than our observation date. API lifecycle and weight terms remain separate.
The date is when the announced service change takes effect, rather than our observation date. API lifecycle and weight terms remain separate.
The date is when the announced service change takes effect, rather than our observation date. API lifecycle and weight terms remain separate.
The date is when the announced service change takes effect, rather than our observation date. API lifecycle and weight terms remain separate.
The date is when the announced service change takes effect, rather than our observation date. API lifecycle and weight terms remain separate.
The date is when the announced service change takes effect, rather than our observation date. API lifecycle and weight terms remain separate.
Model release date from the official announcement.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
Model release date from the official announcement.
Official retirement date: 2026-08-10. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-08-10. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Model release date from the official announcement.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Model release date from the official announcement.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Model release date from the official announcement.
Model release date from the official announcement.
Model release date from the official announcement.
The release date is stated on the official model page. It is separate from API ID suffixes and knowledge cutoffs.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-terra. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-terra. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-terra. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
This version is generally available.
This version is generally available.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Official retirement date: 2027-01-20. Suggested replacement IDs: gpt-realtime-2.1. No paid API probes were run.
Official retirement date: 2027-01-20. Suggested replacement IDs: gpt-audio-1.5. No paid API probes were run.
Official retirement date: 2027-01-20. Suggested replacement IDs: gpt-audio-1.5. No paid API probes were run.
Official retirement date: 2027-01-20. Suggested replacement IDs: gpt-realtime-2.1-mini. No paid API probes were run.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Model release date from the official announcement.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Model release date from the official announcement.
Model release date from the official announcement.
Model release date from the official announcement.
Model release date from the official announcement.
Model release date from the official announcement.
Model release date from the official announcement.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The release date is stated on the official model page. It is separate from API ID suffixes and knowledge cutoffs.
This version is generally available.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Model release date from the official announcement.
Model release date from the official announcement.
Official retirement date: 2026-12-11. Suggested replacement IDs: gpt-5.6-luna. No paid API probes were run.
Official retirement date: 2026-12-11. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-12-11. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-12-11. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-12-11. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-12-11. Suggested replacement IDs: gpt-5.6-terra. No paid API probes were run.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The release date is stated on the official model page. It is separate from API ID suffixes and knowledge cutoffs.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Official retirement date: 2026-12-01. Suggested replacement IDs: gpt-image-2.5-sunburst, gpt-image-2.5-flare. No paid API probes were run.
Official retirement date: 2026-12-01. Suggested replacement IDs: gpt-image-2.5-sunburst, gpt-image-2.5-flare. No paid API probes were run.
Official retirement date: 2026-12-01. Suggested replacement IDs: gpt-image-2.5-sunburst, gpt-image-2.5-flare. No paid API probes were run.
Model release date from the official announcement.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The release date is stated on the official model page. It is separate from API ID suffixes and knowledge cutoffs.
This version is generally available.
This version is generally available.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Official retirement date: 2026-08-10. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-08-10. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-05-07. Suggested replacement IDs: gpt-realtime-1.5. No paid API probes were run.
This version is generally available.
Model release date from the official announcement.
Model release date from the official announcement.
Model release date from the official announcement.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-luna. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-terra. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-terra. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-terra. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-terra. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-image-2.5-sunburst, gpt-image-2.5-flare. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-terra. No paid API probes were run.
Official retirement date: 2026-10-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
Official retirement date: 2026-07-23. Suggested replacement IDs: gpt-5.6-sol. No paid API probes were run.
This version is generally available.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The release date is stated on the official model page. It is separate from API ID suffixes and knowledge cutoffs.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
This version entered public preview.
This version entered public preview.
Model release date from the official announcement.
Model release date from the official announcement.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Official specifications date the release to 2026-04, without an exact day.
Official specifications date the release to 2026-04, without an exact day.
Official specifications date the release to 2026-04, without an exact day.
Official specifications date the release to 2026-04, without an exact day.
This version entered public preview.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Official retirement date: 2026-03-26. Suggested replacement IDs: gpt-5. No paid API probes were run.
This version entered public preview.
This version entered public preview.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Model release date from the official announcement.
Model release date from the official announcement.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
This version entered public preview.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Model release date from the official announcement.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
Model release date from the official announcement.
Model release date from the official announcement.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
This version entered public preview.
Official retirement date: 2026-02-17. Suggested replacement IDs: gpt-5.1-chat-latest. No paid API probes were run.
The release date is stated on the official model page. It is separate from API ID suffixes and knowledge cutoffs.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Official retirement date: 2026-02-12. Suggested replacement IDs: gpt-5-codex-mini. No paid API probes were run.
Model release date from the official announcement.
Model release date from the official announcement.
Model release date from the official announcement.
The release date is stated on the official model page. It is separate from API ID suffixes and knowledge cutoffs.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Official specifications date the release to 2026-02, without an exact day.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
Model release date from the official announcement.
Model release date from the official announcement.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
Model release date from the official announcement.
Model release date from the official announcement.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
This version entered public preview.
Model release date from the official announcement.
Model release date from the official announcement.
Model release date from the official announcement.
Model release date from the official announcement.
This API model was removed. The official recommendation is to migrate to Sonar Reasoning Pro.
This version entered public preview.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Model release date from the official announcement.
Nova 2 Lite became available through the Amazon Bedrock API.
Nova 2 Sonic became available through the Amazon Bedrock API.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The official announcement date, rather than the first API launch or weight upload.
Official specifications date the release to 2025-12, without an exact day.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The release date is stated on the official model page. It is separate from API ID suffixes and knowledge cutoffs.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Official retirement date: 2026-02-17. Suggested replacement IDs: gpt-5.1-chat-latest. No paid API probes were run.
This version entered public preview.
Official retirement date: 2026-02-12. Suggested replacement IDs: gpt-5-codex-mini. No paid API probes were run.
Model release date from the official announcement.
Model release date from the official announcement.
Official maintenance and support for this exact API model have ended. Migration to a current Kimi model is recommended.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Amazon Nova Multimodal Embeddings became available through the Amazon Bedrock API.
Model release date from the official announcement.
Model release date from the official announcement.
Model release date from the official announcement.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The release date is stated on the official model page. It is separate from API ID suffixes and knowledge cutoffs.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
Model release date from the official announcement.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
This version is generally available.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Model release date from the official announcement.
The official announcement date, rather than the first API launch or weight upload.
Official retirement date: 2026-03-26. Suggested replacement IDs: gpt-5. No paid API probes were run.
Model release date from the official announcement.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official announcement date, rather than the first API launch or weight upload.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Official retirement date: 2026-05-07. Suggested replacement IDs: gpt-realtime-1.5. No paid API probes were run.
Official specifications date the release to 2025-09, without an exact day.
Official specifications date the release to 2025-09, without an exact day.
Official specifications date the release to 2025-09, without an exact day.
The official announcement date, rather than the first API launch or weight upload.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Model release date from the official announcement.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Model release date from the official announcement.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Model release date from the official announcement.
Dates and event types follow the official sources. A release does not mean the model became available to every platform or account that day.
This version entered public preview.
This version entered public preview.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Official specifications date the release to 2025-06, without an exact day.
Official specifications date the release to 2025-06, without an exact day.
Official specifications date the release to 2025-06, without an exact day.
Official specifications date the release to 2025-06, without an exact day.
Official specifications date the release to 2025-06, without an exact day.
The official announcement date, rather than the first API launch or weight upload.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Model release date from the official announcement.
This version entered public preview.
This version entered public preview.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
This version is generally available.
Dates and event types follow the official sources. A release does not mean the model became available to every platform or account that day.
Model release date from the official announcement.
Dates and event types follow the official sources. A release does not mean the model became available to every platform or account that day.
This version is generally available.
This version is generally available.
Model release date from the official announcement.
Model release date from the official announcement.
Official specifications date the release to 2025-04, without an exact day.
Official specifications date the release to 2025-04, without an exact day.
Official specifications date the release to 2025-04, without an exact day.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The official announcement date, rather than the first API launch or weight upload.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official announcement records availability in the Audio API, separately from the model’s first release or availability in other APIs.
The official announcement records availability in the Audio API, separately from the model’s first release or availability in other APIs.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Official specifications date the release to 2025-03, without an exact day.
Official specifications date the release to 2025-03, without an exact day.
Official specifications date the release to 2025-03, without an exact day.
Official specifications date the release to 2025-03, without an exact day.
Official specifications date the release to 2025-03, without an exact day.
Official specifications date the release to 2025-03, without an exact day.
Official specifications date the release to 2025-03, without an exact day.
This version is generally available.
Three legacy Sonar online API models were retired.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Model release date from the official announcement.
Model release date from the official announcement.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Official specifications date the release to 2025-01, without an exact day.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official announcement date, rather than the first API launch or weight upload.
Nova Lite became available through the Amazon Bedrock API.
Nova Micro became available through the Amazon Bedrock API.
Nova Pro became available through the Amazon Bedrock API.
Nova Canvas became available through the Amazon Bedrock API.
Nova Reel became available through the Amazon Bedrock API.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The official announcement date, rather than the first API launch or weight upload.
The original model was retired. The old API ID routes to Baichuan3-Turbo-128k.
Model release date from the official announcement.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Anthropic introduced Claude 3.5 Sonnet as the first model in the Claude 3.5 family. The date follows the current official announcement page.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The API became available in the regions and deployment scopes named in the announcement. This is recorded separately from open-weight availability and the model’s first release.
Titan Text Embeddings V2 became available through the Amazon Bedrock API.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Google introduced Gemini 1.5 and its long-context capabilities, with details on initial preview access.
Model release date from the official announcement.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.
Titan Multimodal Embeddings G1 became available through the Amazon Bedrock API.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
The official repository’s release date for this exact weight revision. API launches, papers and repository updates are recorded separately.
Titan Embeddings G1 - Text became available through the Amazon Bedrock API.
The date comes from the official model page. API lifecycle and weight usage terms are checked separately.