> For the complete documentation index, see [llms.txt](https://docs.mindee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mindee.com/crop-models/sdk-integration.md).

# SDK Integration

Use the SDKs to send files to a Crop model and process crop results.

This section helps you choose the right starting point and move through the full integration flow.

### Choose your path

Start with the page that matches your next step:

* [Crop Quick Start](/crop-models/sdk-integration/crop-quick-start.md) ⇒ install a client library, send a file, and get your first result.
* [Crop Result](/crop-models/sdk-integration/crop-result.md) ⇒ access detected items, object types, and optional chained extraction results.
* [Crop Model Overview](/crop-models/crop.md) ⇒ understand how Crop models detect documents or objects on a page.

### Typical SDK workflow

{% stepper %}
{% step %}

#### Create Your Model

[Create your Crop Model](/crop-models/crop.md#create-a-crop-model) on the Mindee platform.

Upload some samples to the [Live Test](/models/live-test.md) to validate the model.
{% endstep %}

{% step %}

#### Install and authenticate

Install the client library for your language.

Prepare your API key and initialize the client.
{% endstep %}

{% step %}

#### Send a file

Set the Crop model's ID and send a file or URL for processing.

Start with polling unless you already use webhooks.
{% endstep %}

{% step %}

#### Process the crop results

Read the list of detected items from the response.

Use each item's object type, page, and polygon in your workflow.
{% endstep %}
{% endstepper %}

### Before you start

Have these ready:

* your API key
* your Crop Model's unique ID
* a sample file for testing
* a language choice for the SDK

### What is specific to Crop models

Crop responses contain a list of detected items found in the source file.

Each item includes an object type and a location.

The location contains a 0-based page index and polygon coordinates.

Object types are returned exactly as configured on the platform.

If extraction chaining is enabled, each crop item can also include an extraction response.

### Shared SDK building blocks

Integration builds on the same client library concepts used across all model types.

* [Client Libraries / SDKs](/integrations/client-libraries-sdk.md)
* [Client Configuration](/integrations/client-libraries-sdk/configure-the-client.md)
* [Send a File or URL](/integrations/client-libraries-sdk/send-a-file-or-url.md)
* [Response Processing](/integrations/client-libraries-sdk/process-the-response.md)
* [Webhook Results](/integrations/webhooks.md)
* [Error Handling](/integrations/problem-database.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mindee.com/crop-models/sdk-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.