Skip to main content

Verified AI Launch Intelligence

See what launched, what changed, and what it costs.

Track AI product launches, model updates, pricing changes and tested workflows. Each record separates official sources, company claims, Kingy testing and third-party evidence so you can see what is known and what remains unverified.

Editorial submissions and sponsor-fit reviews are separate. Payment does not influence Kingy scores, verdicts, rankings, evidence labels, or publication decisions.

Launch tracker

Browse the AI Launch Tracker

Search source-backed launch records, then use common filters first and advanced filters only when you need a narrower view.

Server-rendered fallback. Checking the live launch index…
Showing 19–36 of 73 launches
AI Agents

GitHub Copilot for Jira reaches GA: June 25, 2026 launch record

GitHub Copilot for Jira reached general availability, adding real-time Copilot cloud-agent progress inside Jira, post-session steering and simplified onboarding for connected GitHub repositories.

Recheck due Free: No API: Unknown Open: No
Business-friendlyDeveloper-friendly

The GA release closes useful workflow gaps by returning agent progress and follow-up control to Jira. The integration also moves ticket context into a…

AI Coding Tools

strictKnownMarketplaces for Copilot CLI and VS Code

GitHub launched public-preview strictKnownMarketplaces support in enterprise-managed settings for Copilot CLI and Visual Studio Code, restricting plugin installation to explicitly configured marketplace sources.

Recheck due Free: No API: No Open: No
Business-friendly

strictKnownMarketplaces for Copilot CLI and VS Code provides a useful fail-closed plugin-source boundary, including complete lockdown with an empty list. The public preview does…

AI Coding Tools

OpenAI Codex Remote GA and DigitalOcean Plugin

OpenAI release notes list Codex Remote general availability and a DigitalOcean plugin update for Codex workflows.

Recheck due Free: Unknown API: Unknown Open: Unknown
Launch readiness
6.9 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric

These are launch-record readiness heuristics, not product ratings.

Launch readiness

How complete and reviewable the launch record is, not the quality of the product.

Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.

Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.

Demo evidence

Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.

Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.

Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.

Creator-story fit

Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.

Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.

Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.

Scale
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-07-09.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.

OpenAI's release notes list Codex Remote reaching general availability alongside a DigitalOcean plugin update for Codex workflows (developers.openai.com). AI Engineers and Developers running coding-agent…

AI Coding Tools

Builder.io Visual Plan and Visual Recap Skills

Builder.io published its visual-plan and visual-recap launch article on June 24, 2026, alongside open-source skills for coding-agent workflows.

Recheck due Free: Yes API: Unknown Open: Yes
GitHub tractionTraction signal
Launch readiness
7.0 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric

These are launch-record readiness heuristics, not product ratings.

Launch readiness

How complete and reviewable the launch record is, not the quality of the product.

Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.

Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.

Demo evidence

Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.

Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.

Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.

Creator-story fit

Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.

Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.

Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.

Scale
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-25.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.

Builder.io published open-source visual-plan and visual-recap skills on June 24, 2026, giving reviewers architecture, scope, and risk artifacts before merging coding-agent work (github.com/BuilderIO/skills). AI…

AI Coding Tools

Mem0 Plugin for Pi Code

Mem0 launched the Mem0 Plugin for Pi Code on June 24, 2026.

Recheck due Free: Yes API: Yes Open: Yes
GitHub tractionTraction signal
Launch readiness
7.2 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric

These are launch-record readiness heuristics, not product ratings.

Launch readiness

How complete and reviewable the launch record is, not the quality of the product.

Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.

Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.

Demo evidence

Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.

Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.

Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.

Creator-story fit

Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.

Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.

Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.

Scale
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-25.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.

Mem0 launched its Plugin for Pi Code on June 24, 2026, adding persistent, scoped memory so coding agents retain project context, decisions, and preferences…

AI Coding Tools

GitHub Copilot Auto Mode

GitHub made automatic model selection generally available in Copilot Chat on github.com and GitHub Mobile for all Copilot plans.

Recheck due Free: Yes API: No Open: No
Launch readiness
7.0 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric

These are launch-record readiness heuristics, not product ratings.

Launch readiness

How complete and reviewable the launch record is, not the quality of the product.

Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.

Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.

Demo evidence

Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.

Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.

Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.

Creator-story fit

Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.

Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.

Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.

Scale
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-07-09.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.

GitHub made automatic model selection generally available in Copilot Chat on github.com and GitHub Mobile for all plans, with a documented 10% billing discount…

AI Agents

GitHub Copilot Agent Finder

GitHub released Agent Finder for Copilot, which accepts a plain-language task, searches a selected public or private Agentic Resource Discovery registry, and returns ranked MCP servers, skills, canvases,…

Recheck due Free: Yes API: No Open: No
Developer-friendlyGitHub tractionTraction signal

Agent Finder addresses a real scaling problem: agents should not carry every possible integration in context. Its strongest controls are registry choice, managed settings…

AI Coding Tools

GitHub Code Quality GA

GitHub announced that Code Quality would move from public preview to general availability as a paid product on July 20, 2026.

Recheck due Free: No API: Yes Open: No
Launch readiness
7.0 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric

These are launch-record readiness heuristics, not product ratings.

Launch readiness

How complete and reviewable the launch record is, not the quality of the product.

Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.

Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.

Demo evidence

Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.

Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.

Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.

Creator-story fit

Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.

Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.

Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.

Scale
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-07-09.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.

GitHub scheduled Code Quality's move from public preview to paid general availability on July 20, 2026, with a documented $10 per-active-committer base price plus…

AI Coding Tools

pkg.go.dev API

The Go Team launched a public GET-only v1beta pkg.go.dev API for structured search and package ecosystem metadata, including packages, modules, symbols, versions, known vulnerabilities and imported-by relationships, with…

Recheck due Free: Yes API: Yes Open: Yes
Developer-friendlyGitHub tractionTraction signal

The pkg.go.dev API replaces brittle HTML scraping with an official structured interface and gives AI coding tools a cleaner evidence source. It remains v1beta,…

AI Agents

Hugging Face Serge

Hugging Face introduced Serge on June 12, 2026: an Apache-2.0 GitHub-native pull-request reviewer with repository-owned policy and Action, App or web deployment. The manual web workflow supports editable…

Recheck due Free: Unknown API: Unknown Open: Yes
Developer-friendly

Repository-owned review rules and editable drafts give maintainers concrete controls. Manual web reviews can be edited, discarded or published; the same deployment's webhook route…

AI Agents

OpenAI Ona Acquisition for Codex

OpenAI announced an agreement to acquire Ona, subject to customary closing conditions, with the stated intent to bring Ona’s secure, persistent, customer-controlled cloud execution and orchestration technology into…

Recheck due Free: No API: No Open: No
Business-friendlyDeveloper-friendly

Ona gives OpenAI a credible route toward persistent, governed execution for Codex, but the announcement is a transaction and product-direction statement, not proof that…

AI Coding Tools

GitHub Copilot CLI security review command

GitHub added a dedicated security review command to Copilot CLI.

Recheck due Free: Unknown API: Unknown Open: No
Launch readiness
6.7 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric

These are launch-record readiness heuristics, not product ratings.

Launch readiness

How complete and reviewable the launch record is, not the quality of the product.

Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.

Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.

Demo evidence

Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.

Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.

Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.

Creator-story fit

Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.

Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.

Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.

Scale
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-12.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.

GitHub added a dedicated security review command to Copilot CLI in its June 10, 2026 changelog (github.blog). Developers and Security-Minded Engineering Teams get an…

AI Agents

GitHub Copilot Chat agent-session search

GitHub updated Copilot Chat so it can search and query past Copilot cloud agent sessions in chat.

Recheck due Free: Unknown API: Unknown Open: No
Launch readiness
6.5 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric

These are launch-record readiness heuristics, not product ratings.

Launch readiness

How complete and reviewable the launch record is, not the quality of the product.

Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.

Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.

Demo evidence

Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.

Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.

Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.

Creator-story fit

Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.

Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.

Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.

Scale
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-12.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.

GitHub updated Copilot Chat to search and query past Copilot cloud agent sessions, per the June 10, 2026 changelog (github.blog). Developers and Engineering Teams…

AI Coding Tools

Claude Fable 5 and Mythos-class model launch

Anthropic announced Claude Fable 5 alongside Claude Mythos 5 as a Mythos-class model release for hard knowledge work and coding tasks.

Recheck due Free: Unknown API: Yes Open: No
Traction signal
Launch readiness
8.4 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric

These are launch-record readiness heuristics, not product ratings.

Launch readiness

How complete and reviewable the launch record is, not the quality of the product.

Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.

Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.

Demo evidence

Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.

Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.

Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.

Creator-story fit

Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.

Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.

Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.

Scale
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-07-10.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.

Anthropic announced Claude Fable 5 alongside Claude Mythos 5, a Mythos-class release for hard knowledge work and coding that drew same-day coverage from TechCrunch…

AI Coding Tools

North Mini Code open-source coding model

Cohere announced North Mini Code, a small open-source agentic coding model for developers and coding agents.

Recheck due Free: Yes API: Yes Open: Yes
Traction signal
Launch readiness
7.7 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric

These are launch-record readiness heuristics, not product ratings.

Launch readiness

How complete and reviewable the launch record is, not the quality of the product.

Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.

Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.

Demo evidence

Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.

Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.

Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.

Creator-story fit

Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.

Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.

Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.

Scale
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-12.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.

Cohere released North Mini Code, a small open-weight agentic coding model with downloadable weights on Hugging Face and an available API (cohere.com). Developers, AI…

AI App Builders

ChatGPT Sites

OpenAI launched ChatGPT Sites in preview for eligible ChatGPT Business workspaces, allowing teams to create, host, refine, deploy, and share lightweight websites and web apps through ChatGPT and…

Recheck due Free: No API: No Open: No
Developer-friendly
Launch readiness
6.8 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric

These are launch-record readiness heuristics, not product ratings.

Launch readiness

How complete and reviewable the launch record is, not the quality of the product.

Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.

Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.

Demo evidence

Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.

Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.

Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.

Creator-story fit

Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.

Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.

Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.

Scale
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-07-09.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.

OpenAI launched ChatGPT Sites in preview for eligible ChatGPT Business workspaces — teams create, host, refine, and share lightweight websites and web apps through…

AI Agents

OpenAI expands Codex for every role, tool, and workflow

OpenAI expanded Codex across roles, tools, and workflows, positioning it as a broader professional agent for software-adjacent and knowledge-work tasks.

Recheck due Free: No API: Yes Open: No
Creator-friendlyDeveloper-friendly
Launch readiness
6.1 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric

These are launch-record readiness heuristics, not product ratings.

Launch readiness

How complete and reviewable the launch record is, not the quality of the product.

Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.

Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.

Demo evidence

Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.

Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.

Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.

Creator-story fit

Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.

Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.

Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.

Scale
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.

OpenAI expanded Codex across roles, tools, and workflows, positioning it as a broader professional agent for software-adjacent knowledge work (openai.com). Developers, Product Managers, Data…

AI Agents

Vibe gets to work.

Mistral AI relaunched Le Chat as Vibe, a unified agent for long-horizon work and coding with Work Mode, Code Mode, VS Code support, CLI updates, and mobile access.

Recheck due Free: Yes API: Yes Open: No
Business-friendlyDeveloper-friendlyTraction signal
Launch readiness
7.1 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric

These are launch-record readiness heuristics, not product ratings.

Launch readiness

How complete and reviewable the launch record is, not the quality of the product.

Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.

Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.

Demo evidence

Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.

Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.

Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.

Creator-story fit

Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.

Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.

Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.

Scale
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.

Mistral relaunched Le Chat as Vibe, a unified agent for long-horizon work and coding with Work Mode, Code Mode, VS Code support, CLI updates,…

Daily radar

Latest verified AI launches

A Radar edition publishes only when the day has enough source-ready signal; the tracker continues to show the newest verified records.

No source-ready records are tagged for today yet, so this section is showing the latest public launch records available in the tracker.

AI Models

Qwen4-Max

Summary: Alibaba lists the production Qwen4-Max release on November 16, 2026, with model ID qwen4-max in its Singapore / International deployment. It accepts text, image and video…

Why it matters: Qwen4-Max gives developers a production API endpoint beyond the November 11 Token Plan preview, with text, image and video input and a documented 1-million-token…

Pricing
Alibaba’s standard Singapore / International API tariff lists US$1.50 per million input tokens and US$4.50 per million output tokens for Qwen4-Max, in both thinking and non-thinking modes, up to the 1-million-token context limit. Billed output includes reasoning tokens plus the answer. Other regions, caching and promotions may have different rates; account eligibility was not tested.
Verification
Source-verified; 4 sources
AI Models

Gemini 4 Hydrogen

Summary: Google announced Gemini 4 Hydrogen on November 12, 2026. It is available through free and paid Gemini API and AI Studio tiers, with paid Google AI…

Why it matters: Gemini 4 Hydrogen provides a source-documented hosted option for developers evaluating frequent coding and agent tasks. Measure it on your workload and include thinking…

Pricing
Standard paid Gemini API rates are US$1.50 per million input tokens and US$7.50 per million output tokens, including thinking. Implicit cached input is US$0.075 per million. Free access is rate limited; grounding and other tools can add charges. Review Google’s data-use terms before submitting sensitive code: unpaid-service prompts and responses may be used to improve Google products, with regional and account exceptions.
Verification
Source-verified; 5 sources
AI Developer Tools

Cursor Voice Chat with Agents

Summary: Cursor introduced Voice Chat with Agents on November 6, 2026: two-way spoken conversations in the Agents Window, IDE, web and Cursor for iOS. It is separate…

Why it matters: Cursor Voice Chat adds a spoken interface to coding tasks. Check account eligibility and call limits, and review microphone and privacy settings before trying…

Pricing
A signed-in Cursor account is required. Sessions authenticated with an API key cannot start calls. Daily call limits exist; numeric allowances, free-plan eligibility and feature-specific pricing were not verified.
Verification
Source-verified; 2 sources
AI Models

Gemini Omni 1.2 Flash

Summary: Google launched Gemini Omni 1.2 Flash on November 5, 2026, with general availability through the Gemini API and Gemini for business.

Why it matters: Gemini Omni 1.2 Flash gives video teams longer native clips and editing controls. Check the selected output settings and actual billing units before estimating…

Pricing
The announcement lists US$0.07 per second for 720p video. The API changelog separately lists US$12 per million video output tokens. These are different billing units; check the applicable settings and current terms.
Verification
Source-verified; 2 sources
AI Models

GPT-6 Cyber

Summary: OpenAI introduced GPT-6 Cyber on November 5, 2026, with initial API and Codex access for select approved Daybreak Red customers. Wider access is planned.

Why it matters: GPT-6 Cyber is relevant to security teams eligible for Daybreak Red. Confirm approval, permitted use and pricing before planning work around its restricted API…

Pricing
Standard API rates per million tokens are US$20 input, US$2 cached input and US$100 output. Cache writes are US$25 for 30 minutes or US$50 for 12 hours per million tokens. Context length and processing choices can change rates; confirm approved-access terms and the current pricing table.
Verification
Source-verified; 2 sources
AI Models

ChatGPT Images 2.6

Summary: OpenAI released Images 2.6 on November 4, 2026, in ChatGPT and Codex across all subscription tiers, plus Sunburst and Flare API variants.

Why it matters: Images 2.6 expands image workflows across OpenAI products. Compare Sunburst and Flare on your own edits and check API billing separately from subscription limits.

Pricing
API rates per million tokens for both variants: image input US$8, cached image input US$2 and image output US$30; text input US$5 and cached text input US$1.25. Subscription limits and API billing are separate.
Verification
Source-verified; 2 sources

Plan ahead

Upcoming Deadlines

Future-dated migration, shutdown, and retirement records are separated from today's launches and latest-record lists. These dates are upcoming operational events, not launches that have already happened.

AI Agents

OpenAI Agent Builder shutdown deadline: November 30, 2026

Summary: OpenAI announced the Agent Builder lifecycle deadline: the visual workflow builder is deprecated and scheduled to shut down on November 30, 2026. OpenAI documents two migration…

Why it matters: Export the workflow, select the Agents SDK or a suitable Workspace Agent, and test tools, state, permissions and guardrails before the November 30 shutdown.…

Pricing
Review replacement API costs or Workspace Agent plan requirements before migrating. This record does not estimate your workflow’s implementation or operating cost.
Verification
Recheck due; 3 sources
Uncategorized

OpenAI reusable prompt objects and v1/prompts are scheduled to shut down November 30, 2026

Summary: OpenAI announced reusable-prompt deprecation on June 3, 2026. The documented November 30 shutdown covers reusable prompt objects and v1/prompts. Move managed prompt content into application-owned code…

Why it matters: Treat saved OpenAI prompt objects as a migration dependency before November 30. Move their content and variables into application code, then validate the generated…

Pricing
Pricing unknown
Verification
Recheck due; 5 sources
AI Developer Tools

Three GPT Image API models are scheduled to retire December 1, 2026

Summary: OpenAI schedules gpt-image-1-mini, gpt-image-1.5 and chatgpt-image-latest for API removal on December 1, 2026. Its current deprecation table recommends gpt-image-2.5-sunburst or gpt-image-2.5-flare.

Why it matters: OpenAI schedules gpt-image-1-mini, gpt-image-1.5 and chatgpt-image-latest for API removal on December 1, 2026. Its current deprecation table recommends gpt-image-2.5-sunburst or gpt-image-2.5-flare. Inventory the three…

Pricing
Review the current price of the chosen replacement and measure representative jobs. This lifecycle record does not establish workload cost or promise a cost-neutral migration.
Verification
Recheck due; 5 sources
Explore launch categories, methodology and participation Awards archive, category paths, methodology, submissions, sponsorship and newsletter

Awards archive

Launches of the Week is paused

Prior editions remain available as an archive. Kingy is not currently promising a new weekly awards edition.

Category navigation

Find AI launches by market, workflow, and source signal

Methodology

How Kingy AI Scores Launches

Kingy AI scoring is designed for launch discovery, editorial review, creator planning, and buyer trust checks.

Kingy score

A directional editorial score for launch clarity, source quality, audience fit, pricing visibility, demo usefulness, and practical buyer or creator value.

Demo score

A signal for whether the product can be shown, tested, explained, or compared without relying on vague announcement copy.

YouTube potential

A creator-fit signal for demos, tutorials, before-and-after workflows, explainers, reviews, and audience-specific product education.

Source verification

Records distinguish verified, needs verification, and founder submitted status using official URLs, source links, last-verified dates, and correction paths.

Pricing clarity

Pricing signals favor launches with visible pricing, free-plan status, pricing pages, API access notes, or clear uncertainty when pricing is not public.

Use-case clarity

Launches are easier to evaluate when the audience, workflow, category, demo, and alternative comparison are obvious from public sources.

Founder and sponsor fit

Founder submissions and sponsor interest are routing signals only; editorial review still checks source quality, public claims, demo clarity, and usefulness.

Verification labels

Verified means enough public source evidence is present, needs verification means the record needs more checking, and founder submitted means the entry came through the submission path.

Scores are editorial signals, not scientific benchmarks, paid placements, or guarantees.

Founder submission

Submit Your AI Launch

Founders can send a launch for editorial review when the public source trail is ready to verify.

What to include

  • Product name
  • Website
  • Launch date
  • What launched
  • Official source links
  • Pricing page
  • Demo/video
  • Company info
  • Category
  • Public funding info
  • Screenshots/media

Privacy note

Do not submit secrets, unreleased financials, private customer data, or regulated personal data.

Submit only public product, company, source, pricing, demo, and media details that Kingy AI can review without logging into private systems.

Sponsor path

Sponsor Kingy AI launch coverage

Launching an AI product that needs clear demos, creator education, and buyer trust? Sponsor a Kingy AI video or launch feature.

Brief

Inside The Kingy Brief

Fridays at 09:00 Vancouver time: source-checked AI changes, original tests and one practical thing to try. We skip a week when there is not enough verified material. Free. Unsubscribe anytime.

Models Agents & harnesses Developer infrastructure Products Funding & company moves Pricing watch Under the radar