Available Models
Retrieve the full list of models programmatically:
Supported Document Types
Thedocument model classifies uploaded files into 71 types via the DOCUMENT_CLASSIFIER check, organized into 8 categories:
Identity (11 types)
Financial (19 types)
Tax (9 types)
Employment (7 types)
Property (6 types)
Insurance (6 types)
Commercial (6 types)
Legal (7 types)
Files that do not match a known type are classified as
other.
Analyzing a File
Submit a file for fraud detection viaPOST /v1/detection:
Parameters
Country Hint Behavior
Use the optionalcountry parameter when you want the API to route or annotate the request with an explicit market hint.
- Supported values:
us,mx,br - Matching is case-insensitive
- Leading and trailing whitespace is ignored
- Missing, empty, or invalid values fall back to
us
Response Structure
A detection response contains the following fields:Field Reference
Understanding Results
Likelihood Score
Thelikelihood field is a 0–100% score indicating the probability of fraud or manipulation:
Classification
Theclassification field indicates the document quality assessment — whether the document passed all quality gates and could be properly analyzed. This is separate from the fraud result (likelihood / fraudSeverity).
Reasoning
Thereasoning array contains natural-language explanations of the analysis findings. Each entry describes a specific observation or conclusion from the forensic analysis.
Technical Checks
ThemodelResults.technicalChecks array contains the individual forensic checks performed on the file. The number and type of checks varies depending on the model, file type, and document content.
Each check object includes:
Status Values
Document Model
Thedocument model runs a multi-stage pipeline. First, a series of quality gates determine the classification (whether the document can be properly analyzed). Then, parallel fraud checks analyze the document for manipulation and determine the likelihood score. Additional checks may run depending on the file type and document category.
Object Model
Theobject model returns fraud detection results via the top-level likelihood, fraudSeverity, and reasoning fields. The technicalChecks array will be empty for the object model.
When AI generation or manipulation is detected, a heatmap is included in the files array highlighting the suspicious regions.
Heatmaps
Both thedocument and object models can generate heatmap images that visually highlight the affected regions. Heatmaps make it easy to see exactly where tampering or AI generation was detected.
How Heatmaps Work
- Heatmaps are PNG images overlaid on the original document or image
- Document model: for multi-page PDFs, each page gets its own heatmap (
fd_{id}_heatmap_1.png,fd_{id}_heatmap_2.png, etc.) - Object model: a single heatmap is generated per image (
fd_{id}_heatmap_1.png) - Heatmaps are only generated when manipulation or AI generation is detected
- They appear in the
filesarray withcategory: "heatmap"
Retrieving Heatmaps
Heatmap URLs are included in the detection response underfiles:
File Categories
Error Codes
Tags and Filtering
Pass a JSON object in thetags parameter to attach metadata to your analysis:
Browsing History
Retrieve paginated detection results with sorting and filtering:Query Parameters
Sort Options
fraudDetectionId, fileName, fileSize, fileType, model, likelihood, createdOn