One API call between your workflow and document fraud
POST a document, get a structured JSON verdict in about a minute: clear, suspicious, or likely tampered, with plain-English findings. 130+ forensic checks across 100+ document types - no template setup, no sales call, no document storage.
The problem
Why document verification belongs in the API layer
Most document fraud tooling is built for enterprise procurement: demo calls, annual contracts, per-seat dashboards. Meanwhile the actual work - deciding whether a submitted PDF is genuine - happens inside your onboarding, lending, or claims pipeline, where what you need is an endpoint, not a portal.
Building verification in-house doesn't scale either. One or two forensic checks are a weekend project; maintaining 130+ checks against fraudsters who update their tooling every few months is a permanent team.
An API-first verification layer means fraud detection sits inline in your existing flow: documents are checked at upload, verdicts route the application, and suspicious files never reach downstream systems as trusted data.
What we detect
Forensic signals that expose fraud
Single REST endpoint
POST the file to /api/v1/analyse with your API key. No SDKs required, no callback gymnastics for the simple path - a synchronous verdict in about a minute, with webhooks available for async workflows.
Structured JSON verdicts
Every response includes a verdict (clear / suspicious / likely tampered), a calibrated 0-100 risk score, and itemised findings tied to regions of the document - ready to route programmatically.
130+ forensic checks per call
Font metrics, running-balance arithmetic, metadata fingerprints, text-layer vs raster comparison, ELA, AI-generation detection, and more - all running in parallel on every submission.
100+ document types
Bank statements, payslips, passports, driver's licences, utility bills, academic credentials, invoices, trade licences - across most major issuing countries, with no per-template configuration.
Zero document storage
Documents are analysed in memory and discarded once the verdict is returned. Nothing is retained - which keeps GDPR and data-minimisation reviews short.
BYOK for AI inference
Bring your own OpenAI, Anthropic, Google, or Azure key and the LLM adjudication layer runs on your provider account at cost - or use managed inference with no keys to configure.
The solution
Integrate document fraud detection in an afternoon
TamperCheck is self-serve by design: create an account, generate an API key, and make your first call with the $5 trial credits. The verdict format is stable, documented, and built to be routed on - not read in a dashboard.
How it works
- One endpoint - POST /api/v1/analyse with the file, get JSON back
- Verdict in about a minute - fast enough to sit inline in onboarding
- Webhooks for asynchronous and batch pipelines
- $0.50 per document - usage-based, no subscriptions or minimums
- $5 trial credits on signup - test with your own documents first
- Full API docs at tampercheck.ai/docs, no sales call required
FAQ
Common questions
See it working on your documents
Start with $5 in free credits - no contract, no card required. Upload your first document and get a verdict in about a minute.