We said MAYBE on September 16, 2026. Not settled — due September 16, 2027.
Read this with the caveat. We tested the engine that produced this verdict against 292 launches whose outcomes we already knew, and could not show it predicted which survived. Some of its data sources were also dead at the time of scoring. The verdict stays up, dated and unedited, because a record you can quietly revise is not a record — but it is worth less than it looked when it was written.
Provenance is a real, growing problem with four visible players, but the buyers are enterprises served by Adobe/OpenAI and the standard itself is admitted to have slow adoption. Social evidence is curiosity, not purchase intent, and there is no commercial keyword signal or any profitable small player to prove monetization. This is a plausible early bet on a future market, not a currently monetizable one — SKIP unless the operator has specific C2PA/media-infra expertise and treats it as an open-source wedge, not a revenue project.
There is real market activity — four named products (OpenAI, Adobe, C2PA, Content Credentials) exist in the space and search direction is growing — but social pull is thin and diffuse, and no commercial keywords surfaced. Interest looks like curiosity about the problem ('is anyone leading on digital provenance?'), not people asking to buy an API.
The identified gaps (cheap dev-friendly API, free tier, open SDKs) are real, but every incumbent is a funded giant or a standards consortium, and provenance value is inherently network-dependent — a credential is only worth paying for if platforms and viewers verify and display it, which C2PA/Adobe control. No small profitable player appears in the evidence to prove a solo operator can monetize here.
The strongest case for building: C2PA is an open, published standard with a genuinely awful developer experience, and 'wrap a painful standard in a clean API with a free tier' is exactly how Stripe, Resend and Plausible-style wedges work — the operator doesn't need the ecosystem to be mature, only to be the default tool when it matures. A weekend-scale MVP (sign/verify C2PA manifests via REST, open-source SDKs) is cheap to test and the open-source repo doubles as the acquisition channel, so downside is small and optionality is real.
What is worth more than this page. The register records what became of 6,266 real launches. No engine has to be right for that to be true.