Document verification
for AI agents

Detect fake receipts, forged PDFs, and manipulated documents before your agent acts.

DocVerify helps AI agents verify whether a document is authentic before they trust it. Receipts, payslips, employment letters, bank statements, proof of income, invoices, screenshots, and PDFs can be hand-edited, recompressed, or GenAI-modified while still looking legitimate.

docverify — agent terminal
$ docverify scan --file receipt_march.pdf
 
[agent] Initializing DocVerify v2.0.4...
[agent] Loading forensic models: DTD, RTM, ELA
[agent] Extracting document regions...
STAGE 01 // SURFACE VIEW

What Vision Models See_

LLMs and OCR engines parse text at face value. If a receipt says $9,420.00, they believe it. Zero pixel inspection occurs.

STAGE 02 // TARGET ACQUISITION

Isolating The Anomaly_

DocVerify locks onto the mathematically suspicious total. The digits exhibit anti-aliasing patterns inconsistent with the surrounding font — a telltale sign of post-production editing.

STAGE 03 // DEEP ZOOM

Into The Pixel Grid_

As we zoom past the character boundary, the smooth typography dissolves into raw raster data. Each cell is a single pixel with an RGB color value captured from the receipt surface.

STAGE 04 // RASTER ANALYSIS

Reading The Raw Data_

R,G,B triplets reveal the true color of each pixel. Normal receipt pixels show uniform paper tones (230+). The highlighted anomaly region shows shifted warmth — evidence of re-rendered glyphs.

STAGE 05 // COMPRESSION BASELINE

Error Level Analysis_

We re-compress at JPEG Q95 and measure the delta. Authentic regions: Δ2–18. The anomaly cluster: Δ180–255. This 10× variance is the mathematical fingerprint of tampering.

STAGE 06 // 3D ARCHITECTURE

Dimensional Proof_

Each pixel's height now represents its compression error score. The anomaly region literally rises above the baseline — a 3D topographic map of manipulation that no human eye could detect.

STAGE 07 // VERDICT

Proof Of Manipulation_

Three independent forensic signals converge: compression delta variance, font edge anti-alias mismatch, and DCT block boundary shift. Mathematical certainty: 99.8%.

Scroll to begin analysis
RASTERIZING...
12×8 GRID
QuickMart
1247 Harbor Blvd • Suite 200 • CA 92618
TAX ID: 94-2847561 • TEL: (949) 555-0142
03/14/2026 14:32RECEIPT #8847
Server Rack Unit x2$4,200.00
Enterprise SSD 4TB$1,890.00
Cooling Module Pro$2,340.00
Network Switch 48P$990.00
Subtotal$9,420.00
Tax (8.25%)$777.15
Total$9,420.00
[VARIANCE DETECTED]Anti-alias Δ: 4.2σ above mean
PAYMENT: VISA ****4829 • AUTH: 7X92KM
RASTER DECOMPOSITION // TOTAL REGION
231,233237Δ15
236,230231Δ14
233,230223Δ5
229,228222Δ7
242,248230Δ14
233,229222Δ2
246,242243Δ14
228,228217Δ15
226,236225Δ2
230,228229Δ8
230,233221Δ7
229,235219Δ11
234,239235Δ15
228,222219Δ8
38,5066Δ8
241,240235Δ2
232,225231Δ18
221,228226Δ19
235,246240Δ18
49,3469Δ17
222,231232Δ2
239,241240Δ3
232,232226Δ11
219,226228Δ2
226,235222Δ2
227,235222Δ5
62,5836Δ18
44,3464Δ19
215,185166Δ218
201,185187Δ237
247,210164Δ253
240,211166Δ194
238,210174Δ183
211,186160Δ222
245,237231Δ14
221,228230Δ14
239,242234Δ14
236,247236Δ3
38,5744Δ7
221,226229Δ4
219,204183Δ228
230,214188Δ214
238,207189Δ198
245,208164Δ228
235,189177Δ199
243,218169Δ186
221,228223Δ18
232,230217Δ7
221,224219Δ18
230,235234Δ14
231,232216Δ11
238,243240Δ5
245,194165Δ219
219,189161Δ234
201,187181Δ243
236,199172Δ207
217,181179Δ199
212,191177Δ250
236,235225Δ13
220,229226Δ15
225,237220Δ3
225,233219Δ2
233,243227Δ4
54,6741Δ15
47,4263Δ17
234,229220Δ2
60,6874Δ14
32,5071Δ10
238,231239Δ16
235,230228Δ4
223,237237Δ11
220,233228Δ13
244,241243Δ13
234,247238Δ10
42,6435Δ10
240,242249Δ17
44,5458Δ8
235,238227Δ4
229,226216Δ16
224,234236Δ2
221,228226Δ15
36,3369Δ5
238,249245Δ17
236,230233Δ18
223,229218Δ2
229,234226Δ12
230,231218Δ12
223,230224Δ10
231,242242Δ2
241,244226Δ17
230,232222Δ11
236,244239Δ12
237,240233Δ9
219,230218Δ17
226,230228Δ3
229,224219Δ9

Document Rejected

Confidence: 99.8% • 3 independent signals

PIXEL_MANIPULATIONFONT_VARIANCECOMPRESSION_SHIFT
[SYS.FORENSIC_ENGINE]

Agents can read documents.
DocVerify helps them decide whether to trust them.

Why AI agents need
authenticity checks

AI agents increasingly review uploaded receipts, onboarding documents, proof of income, bank statements, invoices, claims files, and employment records. But document parsing is not document trust.

[01]

Clean OCR

A fake receipt can still produce clean OCR.

[02]

Official Look

A forged PDF can still look official.

[03]

Readable Data

A manipulated bank statement can still be readable by a model.

DocVerify gives agents a dedicated document authenticity check before they approve, reimburse, verify, or escalate. This helps reduce fraud risk in expense review, compliance workflows, onboarding, underwriting, and claims automation.

Engine_Architecture

How DocVerify works

01Compression artifact analysis

DocVerify focuses primarily on image-based compression artifact analysis. Edited, patched, regenerated, or recompressed files often leave subtle traces in the image itself. DocVerify analyzes those patterns to identify hidden manipulation that may not be visible at normal zoom.

02Font & rendering consistency

Inserted text, regenerated content, or altered regions can behave differently from native content in the way characters render, align, and blend into surrounding document structure. DocVerify checks these consistency signals to identify suspicious regions.

03Metadata & edit traces

In parallel, DocVerify inspects metadata and editing traces to determine whether a file appears to have been modified by an editor, passed through a synthetic pipeline, or altered after original creation.

04Vision models for fraud detection

On top of forensic signals, DocVerify uses transformer-based vision models to detect image manipulation, document forgery, GenAI document detection signals, and suspicious edits in scans, screenshots, images, and rendered PDFs.

Result: Document authenticity assessment for agents, not just OCR.

ENGINE_DEMO

See It In Action.

Watch the DocVerify agent analyze a suspected earnings statement — heatmap, verdict, and forensic reasoning — exactly as your AI assistant would see it.

docverify — agent thread

Built for MCP, API, & Skills

DocVerify is built natively for AI agents and tool-calling models.

MCP

Let models natively call document verification inside agent workflows.

Validation API

Integrate document authenticity checks into apps, products, backends, and fraud systems.

Skills

Expose reusable document verification skills inside agent platforms and orchestration layers.

Use cases

Expense fraudFake receipt detectionForged PDF detectionDocument tamperingBank statement verificationProof of incomeEmployment lettersOnboarding reviewClaims screening
SCALE_SECURELY

Pricing

Start free, then scale with one-time request packs or auto-replenishing subscriptions.

Free

10 scans / month

$0.00

Sign up and verify 10 documents per month — no credit card required.

  • 10 free scans / month
  • Standard processing speed
  • Basic support

Pro Auto

500 scans / month

$40.00

Monthly capacity for consistent document review with a lower blended cost.

  • Monthly discounted rate
  • Auto-replenishes every billing cycle
  • Built for steady recurring demand
Best Value

Max Auto

2,500 scans / month

$120.00

The cleanest option for teams that need reliable headroom without manual top-ups.

  • Monthly discounted rate
  • Prevents limits during high-volume runs
  • Priority processing for active teams

Ultra Auto

50,000 scans / month

$1500.00

Designed for enterprise-grade throughput, automation pipelines, and large review queues.

  • Massive monthly grant
  • Enterprise-scale throughput
  • Best for platform-wide automation

FAQ: AI agent document validation

What is document verification for AI agents?

Document verification for AI agents means checking whether a receipt, PDF, bank statement, employment letter, proof of income, or other uploaded file is authentic before the agent relies on it.

Can AI agents detect fake receipts and forged PDFs?

Yes. DocVerify helps agents detect fake receipts, forged PDFs, manipulated screenshots, and altered official-looking files using compression artifact analysis, metadata inspection, font consistency checks, and vision models.

Is DocVerify available as an MCP tool?

Yes. DocVerify is available as an MCP so models can call document authenticity checks natively inside agent workflows.

Is there also an API?

Yes. DocVerify is also available as a validation API for product, backend, and enterprise integrations.

Are Skills available?

Yes. DocVerify Skills are available for agent platforms that support reusable tool and workflow components.

This site uses cookies for authentication and analytics. Uploaded documents are processed in memory and never stored. Learn more