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.
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.
Source-verifiedFree: NoAPI: UnknownOpen: No
Clear use caseBusiness-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…
BrowserAct launched a browser-automation platform spanning an agent CLI and hosted workflow product, with isolated browser sessions, reusable profiles, proxy options, network evidence and human takeover for compatible…
Source-verifiedFree: YesAPI: YesOpen: Yes
Clear use caseDeveloper-friendly
BrowserAct’s launch combines useful session isolation, agent commands and human takeover, but stealth browsers, proxies and reusable profiles increase both capability and misuse risk.…
Kore.ai published the launch of Agent Blueprint Language on June 24, 2026, positioning it as the foundation of its Artemis AI-native enterprise agent platform.
Recheck dueFree: UnknownAPI: UnknownOpen: Unknown
Clear use caseVideo demoTraction signal
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%.
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.
Kore.ai introduced Agent Blueprint Language on June 24, 2026 as the foundation of its Artemis enterprise agent platform, framing agent behavior as a compiled…
Latitude launched V2 for AI-agent monitoring, combining production traces, session search, behavior-pattern signals, recurring-failure discovery, alerts and a coding-agent handoff supplied with issue context.
Source-verifiedFree: YesAPI: YesOpen: Yes
Product Hunt tractionClear use caseDeveloper-friendlyGitHub traction
Launch readiness
7.6 / 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%.
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-28.
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.
Latitude V2 creates a useful closed loop from production traces to recurring-failure signals and a proposed repair. Kingy did not connect telemetry, measure cluster…
AgentX launched an AI-agent evaluation workflow for building test suites, tracing failures, comparing models on quality, cost, and latency, and suggesting fixes before production deployment.
Source-verifiedFree: YesAPI: UnknownOpen: Unknown
Clear use case
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%.
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-16.
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.
AgentX launched an agent-evaluation framework that builds test suites, traces failures, compares models on quality, cost, and latency, and suggests fixes before deployment, shipping…
Google made Gemini Enterprise Workflow Agents generally available with an allowlist, enabling authorized users to create, import, update and run triggered sequences that mix AI automation, connected actions…
Source-verifiedFree: NoAPI: NoOpen: No
Clear use caseDeveloper-friendly
Launch readiness
6.6 / 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%.
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-28.
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.
Gemini Enterprise Workflow Agents offer a more governable structure than an improvised multi-step chat, but GA does not mean open access: the Cloud project…
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,…
Source-verifiedFree: YesAPI: NoOpen: No
Clear use caseDeveloper-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…
AWS announced general availability of Web Search on Amazon Bedrock AgentCore, providing a managed way for agents to retrieve current web information through AgentCore Gateway.
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%.
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-16.
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.
AWS made Web Search on Amazon Bedrock AgentCore generally available, a managed way for agents to retrieve current web information through AgentCore Gateway, with…
Genspark announced a $100 million Series B extension that it says brought the round to $485 million at a $2.6 billion post-money valuation, alongside a chief revenue officer…
Source-verifiedFree: YesAPI: NoOpen: No
Clear use caseVideo demoBeginner-friendlyBusiness-friendly
The extension increases Genspark’s stated capacity to pursue enterprise distribution, but capital raised is not product validation. The funding, valuation, ARR, investor, model-count and…
Microsoft made Copilot Cowork generally available worldwide inside Microsoft 365 Copilot for complex, multi-step work.
Recheck dueFree: UnknownAPI: UnknownOpen: Unknown
Clear use case
Launch readiness
7.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%.
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.
Microsoft made Copilot Cowork generally available worldwide inside Microsoft 365 Copilot, moving the assistant toward delegated multi-step work across documents, communications, and organizational context…
Microsoft made Work IQ APIs generally available for agents that need permission-aware Microsoft 365 context, tools, and actions.
Recheck dueFree: NoAPI: YesOpen: No
Clear use case
Launch readiness
8.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%.
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.
Microsoft made Work IQ APIs generally available on June 16, 2026, giving agents permission-aware Microsoft 365 context, tools, and actions with consumption-based Copilot Credits…
AppViewX announced Agent Identity Security in private preview for discovering, governing, securing, and monitoring enterprise AI agents, credentials, MCP connections, models, and access paths.
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%.
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-16.
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.
AppViewX announced Agent Identity Security in private preview — discovering, governing, securing, and monitoring enterprise AI agents, credentials, MCP connections, models, and access paths…
CrowdStrike announced Continuous Identity for AI Agents, a Falcon Next-Gen Identity Security capability intended to give agents verifiable workload identities and authorize each action using owner, caller, device-risk…
Source-verifiedFree: NoAPI: NoOpen: No
Clear use caseBusiness-friendly
CrowdStrike’s continuous-authorization model addresses a real weakness in long-lived agent credentials, and the announcement is unusually specific about owner, caller, device and delegation context.…
OpenAI launched a global program for firms that build, sell and deliver AI solutions, with Select, Advanced and Elite tiers, a public partner directory, planned specializations and a…
Source-verifiedFree: NoAPI: NoOpen: No
Clear use caseBeginner-friendlyBusiness-friendly
The Partner Network gives enterprises a more structured way to discover OpenAI-focused delivery firms and gives partners clearer tiers and program infrastructure. A directory…
Hugging Face launched Serge, an open-source pull-request reviewer that uses OpenAI-compatible models, loads policy from the default branch and runs as a GitHub Action, GitHub App or staged…
Source-verifiedFree: YesAPI: YesOpen: Yes
Clear use caseDeveloper-friendly
Serge’s repository-owned policy and editable draft workflow make human judgment more explicit than in many automated reviewers. Its three modes also create different token,…
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…
Source-verifiedFree: NoAPI: NoOpen: No
Clear use caseBusiness-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…
GitHub released Agentic Workflows in public preview, compiling natural-language Markdown into standard GitHub Actions workflows that run coding agents for issue triage, CI analysis, documentation and other repository…
Source-verifiedFree: NoAPI: YesOpen: Yes
Clear use caseDeveloper-friendly
Launch readiness
7.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%.
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-28.
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 Agentic Workflows offers credible defense in depth through read-only defaults, sandboxing, a network firewall, safe outputs, compile-time validation and threat scanning. Those controls…
GitHub updated Copilot Chat so it can search and query past Copilot cloud agent sessions in chat.
Recheck dueFree: UnknownAPI: UnknownOpen: No
Clear use caseVideo demo
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%.
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…
No source-ready records are tagged for today yet, so this section is showing the latest public launch records available in the tracker.
AI Voice/Audio Tools
gamedai live AI sports radio
Summary: gamedai says its live AI sports-radio service went live on August 7, 2026 for the NFL preseason. The launch page describes coverage for all 16 Week…
Why it matters: gamedai is an interesting vertical-agent launch because it joins live data, retrieval, voice generation, and an evaluation layer around one narrow listener job. The…
Pricing
The official homepage lists a free Casual tier, Premium at $9.99 per month with a seven-day free trial, and a $99.99 one-time Lifetime unlock. The reviewed Join Now link returned a deployment-not-found page, so signup and billing availability were not independently confirmed.
Summary: Liquid AI released the base and post-trained LFM2.5-2.6B checkpoints on August 4, 2026. The post-trained text model targets agentic workloads and ships in native, GGUF, MLX,…
Why it matters: LFM2.5-2.6B is a credible option for high-volume, privacy-sensitive local agents where compact size and tool use matter more than frontier reasoning. Treat it as…
Pricing
The model weights are downloadable under Liquid AI's LFM1.0 license. Liquid AI did not announce a paid hosted API price for this release, and the reviewed Hugging Face page says no inference provider currently deploys the model. Self-hosting avoids a vendor per-token fee but still carries hardware, electricity, engineering, and support costs.
DeepSeek V4-Flash-0731 launches in API beta with native Codex support
Summary: DeepSeek released DeepSeek-V4-Flash-0731 as the official V4-Flash API public beta. The checkpoint keeps the preview model’s architecture and size but adds new post-training, native Responses API…
Why it matters: Worth testing for cost-sensitive coding-agent workloads because it combines native Codex support, a one-million-token context window, very low API pricing and MIT-licensed weights. Treat…
Pricing
$0.0028 per 1M cached input tokens; $0.14 per 1M uncached input tokens; $0.28 per 1M output tokens. DeepSeek says future peak-hour prices will be 2× regular rates, with no effective date announced.
OpenAI releases Codex Security CLI and TypeScript SDK in limited beta
Summary: OpenAI published the Codex Security command-line client and TypeScript SDK. The CLI supports repository and change review, bulk scans, history, CI workflows, SARIF output and false-positive…
Why it matters: The CLI and SDK make Codex Security easier to insert into repeatable engineering workflows and expose useful integration primitives such as typed findings, SARIF,…
Pricing
OpenAI does not publish self-serve Codex Security pricing in the reviewed documentation. CLI and SDK access is limited to approved beta customers and partners through an OpenAI account team. Commercial terms, quotas and any Trusted Access for Cyber requirement are account-specific.
Model Context Protocol 2026-07-28 specification goes final
Summary: The final Model Context Protocol 2026-07-28 specification became the current authoritative protocol version. It replaces connection-level state with self-contained requests, moves capability negotiation to each request…
Why it matters: The 2026-07-28 MCP specification makes a consequential architectural trade: stateless, self-contained requests can simplify scaling and recovery, but implementations must now negotiate and validate…
Pricing
MCP is an open protocol specification, not a paid hosted product. Implementations, infrastructure, models, connectors and support can carry separate costs. The official specification and governance pages are the authority for the protocol boundary.
Summary: Microsoft announced Project Perception, an agentic security system that coordinates specialized red, blue, and green agents inside Microsoft Defender.
Why it matters: The launch brings attack simulation, defense testing, and threat-scenario planning into one Microsoft Defender workflow. Its practical effectiveness and cost remain unproven until security…
Pricing
Microsoft says Project Perception uses consumption-based, pay-as-you-go pricing measured in Security Compute Units (SCUs). Different agents consume SCUs at different rates; Microsoft did not publish numeric SCU rates in the checked launch sources.
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 Developer Tools
Google Imagen 4 API shutdown window: August 17, 2026
Summary: Google announced that imagen-4.0-generate-001, imagen-4.0-ultra-generate-001 and imagen-4.0-fast-generate-001 are deprecated. Its deprecations table lists August 17, 2026 as the earliest possible shutdown date and recommends gemini-3.1-flash-image.
Why it matters: Plan against August 17 while preserving Google’s wording: the deprecations page says listed dates are the earliest possible shutdown dates and that exact timing…
Pricing
There is no separate migration fee. Replacement Gemini API image generation follows current Google pricing and quota terms; teams should compare the selected model, image output, prompts and workload mix on the live pricing page.
OpenAI Assistants API migration deadline: August 26, 2026
Summary: OpenAI’s Assistants API reaches its shutdown deadline on August 26, 2026. OpenAI recommends Responses API and Conversations API, with documented mappings from Assistants to configuration or…
Why it matters: Treat August 26 as an operational deadline, not a feature launch or a find-and-replace exercise. OpenAI documents object and orchestration changes, including explicit tool-loop…
Pricing
There is no separate migration fee. Replacement API usage is billed under current OpenAI API pricing, while engineering, regression testing, data migration, observability and rollback work remain implementation costs.
Google retires Gemini Robotics ER 1.6 Preview on August 31
Summary: Google announced that gemini-robotics-er-1.6-preview will shut down on August 31, 2026, and its deprecation table names gemini-robotics-er-2-preview as the replacement.
Why it matters: Google announced that gemini-robotics-er-1.6-preview will shut down on August 31, 2026, and its deprecation table names gemini-robotics-er-2-preview as the replacement. Kingy’s action: Replace the…
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.