Verify before OCR
Run the authenticity check before your parser extracts totals, balances, names, dates, or IDs from a manipulated file.
Add a forensic document verification API to screen receipts, PDFs, bank statements, IDs, and payment screenshots before OCR, KYC, AP, underwriting, or AI agents act on extracted data.
curl -X POST https://docverify.app/api/analyze \ -H "X-API-Key: sk_live_..." \ -F "file=@invoice.pdf" \ -F "include_heatmap=true" \ -F "ai_review=true"
{
"result": {
"risk": "high",
"signals": ["metadata_anomaly", "text_region_edit"],
"heatmap_url": "..."
}
}Run the authenticity check before your parser extracts totals, balances, names, dates, or IDs from a manipulated file.
Return a structured score, forensic signals, and heatmap evidence so your product can approve, request a replacement, or escalate.
Give AI agents a document-trust tool before they summarize uploaded PDFs, approve expenses, or move data into downstream systems.
Integration path
The API sits between upload and trust. It is useful anywhere a user-submitted file can become evidence in an automated decision.
Create an API key in the DocVerify console.
Send a PDF, screenshot, scan, or image to /api/analyze.
Use the JSON result to continue automation or trigger review.
Developer resources
Authentication, upload formats, response fields, billing states, and error handling.
OpenA practical walkthrough for adding document verification to an existing workflow.
OpenCategory page for AI document verification, KYC, AP, finance, and agent use cases.
OpenA document verification API lets a product send an uploaded file to a verification service and receive a structured authenticity assessment. DocVerify checks for manipulation signals before OCR, onboarding, AP, underwriting, or agent workflows trust the file.
No. OCR reads text from a document. A document verification API checks whether the uploaded document appears authentic, edited, recompressed, synthetic, or suspicious before extracted text is trusted.
DocVerify accepts PDFs and common image formats including JPEG, PNG, WebP, HEIC, TIFF, BMP, and GIF. Typical API use cases include receipts, invoices, bank statements, IDs, payslips, payment screenshots, and onboarding documents.
Put it at file intake: immediately after upload and before OCR, approval rules, KYC review, expense reimbursement, underwriting, or AI agent actions use the file as evidence.
Start with the API docs, then connect DocVerify to the workflow where uploaded files become trusted evidence.
This site uses cookies for authentication and analytics. Free-tier uploads may be retained to improve our models; paid-tier uploads are never stored. Learn more