What is available now
There is no public developer API yet: no customer accounts, billing, API credentials, usage contract or availability promise. Joining the waitlist records your interest and intended use. It does not purchase access, start a subscription, send an email or authorize any third-party model call.
Tell us the decision you support
Join using an address you are comfortable providing. This form records a developer API use category; it does not ask for private examples, account secrets, identity documents, or a free-text description. Editorial triage, catalog review, and checking disclosed generated assets may require different evidence and escalation paths. Any future service must distinguish individual results from batch processing and keep a human responsible for reviewing uncertain outputs. Detailed requirements can be discussed after a separate contact.
Expected evidence boundaries
A future API should keep metadata observations, validated provenance, model estimates and third-party provider responses as separate fields, because they are not interchangeable. C2PA data needs signature and trust validation, and SynthID requires access to an official detection route. Image Evidence offers neither validated C2PA signatures nor a SynthID integration today.
Consent and waitlist handling
The form requires explicit agreement to store your email and intended use for evaluating early-access interest. This page records your intended use as developer API. Consented entries are saved in Cloudflare D1 with campaign attribution, a referring domain when provided, and consent and submission times. No email is sent on submission, and it does not subscribe you to unrelated marketing. Unconverted entries are deleted after twelve months. The privacy notice explains contact and deletion requests.
Uses we will not support
The product does not offer watermark removal, detector evasion, Humanizer features, face recognition, image-to-person search, or pages accusing specific real people. Results are informational and cannot function as legal authenticity opinions. An integration must not turn an uncertain estimate into an automatic adverse decision about a person. Pricing, model evaluation, legal terms and operational limits will be published before any API launch.
What would an AI image detection API return?
Our design goal is a structured report rather than a single score: metadata observations, provenance results with their validation status, model estimates with uncertainty, and clear notes on what was not checked. The final contract will be published before launch.
Who is the API for?
Teams that review images as part of a human workflow, such as editorial triage, marketplace listing review or checking disclosed generated assets. It is not intended for automatic adverse decisions about people, face recognition or identifying individuals.