How it works
How Hesper AI works
A deep dive into the detection pipeline — from document receipt to fraud verdict in under 80 milliseconds.
Where Hesper AI fits in your pipeline
Your application sends the document
Before passing a document to your OCR pipeline, send it to the Hesper AI /v1/analyze endpoint via a standard multipart POST request. We accept PDFs, PNGs, JPEGs, and TIFFs up to 50MB. No preprocessing or conversion required.
Pixel-level forensic analysis
Our computer vision models scan the document at the pixel level — detecting cloning artifacts, brightness edits, compression inconsistencies, and other traces left by editing software including Photoshop, GIMP, and AI image generators.
Font and typography analysis
We extract and analyse every character in the document, detecting inconsistent font weights, spacing anomalies, and characters that don't match the document's declared font metadata — common signs of text replacement.
Metadata and structural validation
Document metadata is cross-referenced against the visual content. Creation timestamps, software fingerprints, and embedded color profiles are checked for inconsistencies that indicate post-processing.
Verdict returned in under 80ms
A structured JSON response is returned: a fraud score from 0–100, a verdict (CLEAN / SUSPICIOUS / LIKELY_FRAUD), an array of findings with pixel coordinates, and a confidence rating. Your pipeline continues normally for clean documents, or you halt for review.
The API request and response
Request
Response
Latency and throughput specs
Ready to integrate?
Get API access and analyze your first document in under 5 minutes.