> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/plugins/first-party-ango-plugins/captioning-qa.md).

# Captioning QA

## Overview

The Captioning QA plugin is a model plugin that creates visual QA attachments for captioning or description review workflows.

Use this plugin when a task contains bounding boxes with descriptions or OCR text and you want compact image attachments showing each crop next to its text.

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td align="center">Captioning QA</td><td data-object-fit="contain"><a href="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2Fgit-blob-92875d360d8c9c36ed34dd93f606f44733307179%2Fcaptioning-qa.png?alt=media">captioning-qa.png</a></td></tr></tbody></table>

## Plugin Functionality

The Captioning QA plugin reads the current task annotations, generates summary images, uploads those images to S3, and attaches them back to the asset.

For each image in the asset, the plugin creates an attachment containing cropped bounding-box regions and their corresponding text. The text is taken from:

* OCR text on the bounding-box annotation, when present.
* A nested classification titled `description`, when OCR text is not present.

For multi-image assets, the plugin can also create a correspondence attachment. It looks for a nested classification titled `corresponding id` and uses that value to group related object IDs across the first two images.

{% hint style="info" %}
If the task has no tool annotations, the plugin finishes without adding attachments.
{% endhint %}

### Supported Data Types

* Image
* Multi-Image Assets

### Supported Annotation Tools

* Bounding Box
* OCR text on bounding boxes
* Nested classifications named `description`
* Nested classifications named `corresponding id` for correspondence views

## Plugin Configuration

By default, the plugin uploads generated QA attachments to an Ango-managed S3 location. You can provide your own storage settings in the **Config JSON** field.

```json
{
  "storage_id": "",
  "bucket_name": "",
  "folder": ""
}
```

* **"storage\_id":** Storage integration ID used to upload the generated QA images.
  * Example:
    * <kbd>"storage\_id": "storage\_id\_here"</kbd>
* **"bucket\_name":** Name of the S3 bucket where the generated images should be uploaded.
  * Example:
    * <kbd>"bucket\_name": "acme-qa-attachments"</kbd>
* **"folder":** Folder prefix where generated images should be uploaded.
  * Example:
    * <kbd>"folder": "captioning-qa/"</kbd>

{% hint style="warning" %}
If you provide custom storage settings, make sure the storage integration has permission to upload files and that generated attachment URLs can be accessed by Ango Hub users who need to review them.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.imerit.net/plugins/first-party-ango-plugins/captioning-qa.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
