For the complete documentation index, see llms.txt. This page is also available as Markdown.

Crop Model Overview

Automatically identify the borders of documents on each page, and match one to a category.

Use Cases

Process different documents sent on the same page (usually a photo). The result has both the location (page and coordinates) and the class for each document identified, allowing for complex workflows.

A file sent to the Crop Model may have any number of pages, within limits. Use the page index in the results to identify on which page the document was found.

Some common examples:

  • Single photo of a bunch of receipts on the table

  • Front and back of an ID card, each on the same PDF page

  • Remove the background from all documents in a multi-page PDF

Create a Crop Model

Crop models are always custom, there are no templates available in the Catalog. This keeps Crop models flexible for different documents and workflows.

Each Crop model gets its own unique model ID when you create it.

  1. To create a Crop model, click on Models, and then click on Create your document AI model.

  2. Scroll to the Document Utilities section, click on Crop.

  3. A pop-up will appear, allowing you to enter the classes you want. Each class corresponds to a document type possibly present in the pages you want to process. For example, if the files you are processing contain ID cards and passports, set the classes as: ID Card Front, ID Card Back, Passport.

Add the class OTHER if you need the model to identify documents that are not one of the explicitly defined classes.

  1. Once ready, click on Create Utility to create your custom Crop Model. This step will also generate the model's unique ID.

  2. You can now use the Live Test tab to process documents, and the Utility Configuration to update your classes.

Your utility is now available in your Models tab:

Here is a step-by-step tutorial that shows you how to properly create a Crop Utility :

spinner

Integration

Class names will be returned exactly as defined on the platform in the return, spaces and capitalization included.

If the class names are changed on the platform, the change in the API return will be immediate for all new files sent.

Once your Crop model is created and tested, integration documentation is provided in the "Documentation" page.

Last updated

Was this helpful?