Skip to content

Product capabilities

One API contract, from detection to decision.

Scanverion combines document and image operations around the objects found in each upload. Your backend receives connected results instead of stitching together unrelated service responses.

POST /ai/document-processing
  1. 01Upload
  2. 02Detect
  3. 03Process
  4. 04Respond
Synchronous · typed · object-level

Supported documents

See what Scanverion can read.

Clearly invalid AI specimens are based on linked public document layouts. The cards distinguish an API category from the structured Scanner output that has been implemented and tested.

Fictional AI specimen of a Slovak business invoice

Invoice

Layout based

Layout-based invoice extraction

Example fields
API category

Invoice

Example fields
invoiceNumbersupplierNamecustomerNamepaymentReferencelineItemsgrossTotal
Layout reference: Original Scanverion AI invoice specimen · Fictional demo

AI-generated demo images use fictional data, visible SPECIMEN markings and invalid machine-readable values. They are not real or customer documents.

Fictional AI application form with checkboxes, portrait, signature and sample codes

Generic documents

Visual operations work beyond known document types.

Checkboxes, barcodes, signatures, faces, blur and rotation can be analysed on forms, contracts, scans and unknown documents. A dedicated Scanner profile is not required.

  • Detection: Locate documents and other objects.
  • Rotation: Measure document orientation.
  • Blur: Evaluate image sharpness.
  • BarcodeReading: Read QR and linear barcodes.
  • CheckboxDetection: Evaluate checkbox regions supplied in the request.
  • SignatureDetection: Detect a visible signature.
  • FaceDetection: Locate visible faces.
  • FaceExtraction: Return detected face regions.
Example fields

CheckboxDetection uses CheckboxDefinitions supplied with the request. Full-image scanning can also return requested ScannerFields.

Layout reference: Original Scanverion AI application form · Fictional demo

Country support

Coverage follows the document standard and issuing layout.

Passport MRZ data is standardized globally. Identity cards and other national documents require a tested layout for that country and document generation.

01

Passports

MRZ fields from any passport with a readable ICAO TD3 MRZ
Additional printed layouts tested
SKFICHUA
02

National identity cards

Structured fields for supported front and back layouts
Country layouts tested
SKCZHURODEATPL
03

Slovak national documents

Structured fields for the supported Slovak document types
Document types supported
Residence permitsDriving licencesVehicle registration I/IIDisability cards

Capability map

Request only the signals your workflow needs.

Compatible operations share the same detected objects and return through a single response envelope.

01

Object detection

Find documents, vehicles, faces, barcodes, checkboxes, and signatures with normalized bounds and confidence.

02

Document scanning

Extract identity-document fields while keeping the scanner output attached to the detected document.

03

Image quality

Measure blur and rotation before poor source images reach downstream verification or archive workflows.

04

Validation

Use dedicated resources for lost-or-stolen card checks and postal address resolution.

05

Operational control

Track operation-level usage, credits, budgets, subscriptions, API keys, and workspace access.

Where it fits

Concrete workflows, not abstract AI labels.

These patterns show how capabilities combine. The API remains explicit, so teams can adapt the operations to their own risk and review process.

01

Identity onboarding

Detect the identity card, extract its fields, locate the portrait, and check source-image quality before continuing the onboarding flow.

Detection · Scanner · Face · Blur
02

Document intake

Turn uploaded documents into structured records while preserving the source object, its bounds, and extraction status.

Detection · Scanner · Rotation
03

Quality gates

Reject or route images that are blurred, rotated, or missing expected visual signals before manual review.

Blur · Rotation · Signature
04

Vehicle workflows

Recognize supported vehicle imagery through an explicit vehicle processing resource using the same synchronous contract style.

Vehicle model · Detection

Integration principles

Built to be operated by backend teams.

  • TypeScript
  • Python
  • .NET
  • CLI
  • Postman
  • Bruno
  • OpenAPI