Publisher workflow
AI detector for publishers
AI-content review workflows for publishers that need batch checks, report exports, and provenance-aware QA.
Run a signal check
No detector model loads until you press Check.
Current support
Publishers can start with browser checks and local bulk jobs before moving to paid queues, account history, and API integrations.
What this checks
- Bulk jobs create saved report links for each article row.
- CSV, JSON, and print-ready PDF exports support editorial handoff.
- API keys preview how CMS integrations will authenticate checks.
What this does not prove
- Production publisher workflows still need account permissions and retention controls.
- Bulk text checks do not inspect original file provenance unless files are uploaded.
- Signal reports should not be converted into automatic rejection rules.
FAQ
- Can this prove whether content was written by AI?
No. AI Detect reports signals such as provenance metadata, watermark support status, and statistical text risk. It does not claim legal or authorship proof.
- Does text leave my browser during a local check?
Browser-default checks run local text features and provenance checks after you press Check. Server enhanced checks are separate and will be labelled before use.
- Why can a result be unknown?
Many providers do not expose public watermark detectors, and metadata can be absent or stripped. Unknown is a valid result when no reliable public signal exists.
Workflow upgrade
Need repeatable reviews?
Move from one-off checks to saved reports, batch review, and API-ready signal records when the workflow needs it.