Terms for using VeracityAPI.
These terms govern access to VeracityAPI websites, demos, APIs, SDKs, MCP tools, and related integrations. By using VeracityAPI, you agree to use it as a workflow-risk and content-trust tool, not as forensic proof of authorship, identity, truth, or legality.
Last updated: May 11, 2026. Contact: hello@veracityapi.com. Informational terms; not legal advice.
1. Service purpose
VeracityAPI provides probabilistic content-trust, specificity, provenance, synthetic-media workflow-risk, and recommended-action signals for text, image URLs, audio URLs, and private-beta video URLs. Outputs are designed to help route workflows to allow, revise, human_review, or reject.
2. No forensic or legal determination
VeracityAPI outputs are not proof that content is AI-generated, human-authored, true, false, cloned, infringing, safe, illegal, or legally actionable. Do not use the service as the sole basis for academic discipline, employment decisions, credit, housing, insurance, legal claims, identity verification, or other high-stakes determinations.
3. Accounts, API keys, and billing
You are responsible for securing your account, sessions, API keys, and integrations. Usage may be billed by request, character unit, or credit balance as shown on the pricing page or account console. Keep keys out of client-side code, public repositories, prompts, and logs.
4. Acceptable use
You may not use VeracityAPI to violate law, abuse rate limits, reverse engineer or attack the service, submit malware or unlawful content, misrepresent outputs as forensic evidence, or build systems that make unsupported high-stakes automated decisions without human review and independent evidence.
5. Content and data handling
You retain responsibility for content you submit and must have the rights and permissions needed to process it. VeracityAPI is designed to avoid raw text storage and does not store raw image, audio, or video bytes, base64, frames/contact sheets, or full media URLs for media analysis. See the Privacy page for current retention details.
6. Third-party providers
VeracityAPI may use third-party model, infrastructure, payment, email, analytics, or hosting providers to operate the service. Their availability and policies can affect latency, uptime, and processing.
7. Availability and changes
The service is provided on a beta/production-evolving basis. Features, prices, models, limits, endpoints, SDKs, MCP tools, and response fields may change. We aim to keep backwards compatibility for documented production endpoints when practical.
8. Disclaimers and limitation of liability
VeracityAPI is provided as-is and as-available, without warranties of accuracy, availability, fitness for a particular purpose, or non-infringement. To the maximum extent permitted by law, VeracityAPI and its operators are not liable for indirect, consequential, special, punitive, or lost-profit damages arising from use of the service. Aggregate liability is limited to fees paid for the service in the prior three months, unless applicable law requires otherwise.
9. Termination and contact
We may suspend or terminate access for abuse, security risk, non-payment, or violation of these terms. Questions, notices, deletion/export requests, and security reports can be sent to security@veracityapi.com.