VeracityAPI is not an AI detector. It is a routing linter for AI outputs.
The product wedge: action plus evidence for agent workflows, not forensic authorship proof.
AI detector is the market phrase, but the operational problem is shippability. VeracityAPI does not care who wrote a draft; it cares whether an agent should publish, revise, review, or reject it.
For text, the API looks for AI slop, generic phrasing, weak specificity, and unsupported claims. For image, it uses synthetic-media and provenance-risk language rather than calling media slop.
The output is designed for software branches: recommended_action, primary_reason, evidence, limitations, and optional auto_revise for text. The longer-form rationale for why the category is splitting into authorship-likelihood detectors and workflow-routing APIs is in 'Why the AI-detection category is splitting.'
Required caveat: VeracityAPI is a workflow-routing API, not forensic authorship proof. See /methodology for what we claim and don't claim.
Bernard Huang · Founder, VeracityAPI
Co-founded Clearscope and bootstrapped it to 7-figure ARR over 10 years of working with editorial and content teams at companies like Nvidia, HubSpot, Adobe, IBM, and Condé Nast. Now building VeracityAPI — content trust infrastructure for autonomous agent workflows.