Enterprise API

Document Trust Score API

One normalized risk score per document — backed by per-field forensic evidence.

Fraud and risk engineering teamsUnderwriting and decision platformsTrust & safety teamsInsurance and claims tech

Forensic detection delivered as one API call

One POST returns AI-generation indicators, tampering regions, metadata drift, math reconciliation, and a verdict — designed for risk engines, not onboarding funnels.

▸ Document Analysis · LiveID: 8829-XQ
Risk score: High · 94%Signals matched: 12,042

Metadata deep-dive

Inspects EXIF, software signatures, edit history, and structural fingerprints.

EndpointPOST /v1/verify
Latency p95~6s per document
WebhookSigned verdict event

Privacy-first by design

Originals are processed in encrypted memory and removed after analysis. Reports stay redacted by default.

No training on your data
Team & admin controls
▸ 01 · The Problem

Why identity-onboarding APIs miss document-level fraud

Engineering teams need a single normalized number to feed into decisioning — but they also need the per-field evidence behind it for review and audit.

TrueDoc returns a trust score for every verified document, alongside the structured evidence map that drove it.

▸ 02 · Fraud Signals

What we look for

Cross-checked across 4+ vectors
▸ Primary signal

Hard yes/no verdicts that hide nuance

Detected at pixel + metadata + structural layers

Black-box scores with no underlying evidence

Scores that don't generalise across document types

Hidden recalibrations that break downstream thresholds

What gets checked

All document types supported by the verification API
IDs, statements, invoices, receipts, contracts
Screenshots and image proofs
Multi-page documents
▸ 03 · Workflow

From upload to verdict

01

POST /verify

Send the document; the response includes a trust score plus findings.

02

Read the score

Normalized number combining forensic, structural, and AI-generation signals.

03

Inspect the evidence

Per-field findings explain the score — useful for review and audit.

04

Wire into thresholds

Auto-accept above your threshold, route mid-range to review, escalate the lowest scores.

Example response shape

Every /verify response includes a trust score, an ordered list of findings (with confidences and field pointers), an AI-generation indicator, and a stable verdict ID.

The verdict ID links to the immutable record in the enterprise portal — useful for review and audit.

How teams use the score

Auto-accept high scores in low-risk workflows to reduce manual review volume.

Route mid-range scores to a reviewer queue with the evidence pre-attached.

Trigger step-up checks (additional document, biometric, manual review) only on the lowest scores.

Limitations

No score is a 100% verdict. Treat it as a strong signal, not a single source of truth.

Re-encoded, low-resolution, or heavily compressed files reduce signal strength and may lower confidence.

Run a real document. Get a forensic verdict.

No credit card. Redacted report in under a minute.

▸ FAQ

Frequently asked questions