> For the complete documentation index, see [/llms.txt](/llms.txt).

> Source: /docs/capabilities/extract/prebuilt-extraction

# Prebuilt information extraction

> Deprecation notice
>
> Prebuilt Information Extraction was deprecated on May 6, 2026. Please use [Universal extraction](/docs/capabilities/extract/universal-extraction) instead.

## What is prebuilt information extraction?

Built on highly accurate [Document OCR](/docs/capabilities/parse/document-ocr), Upstage's prebuilt information extraction models excel at identifying and extracting predefined key information within specific documents types.
Prebuilt information extractors are ideal for automating repetitive tasks--such as data entry, compliance checks, or invoice processing, where specific fields must be extracted consistently and accurately with large throughput.

## Why use Upstage prebuilt information extractors?

- **Tailored for specific document types**:
  Unlike [universal information extraction](/docs/capabilities/information-extraction/universal-information-extraction) models,
  Upstage prebuilt information extractors are fine-tuned for specific document formats, achieving higher accuracy, typically around 90-95% for tens to hundreds of keys.
  This level of precision makes them ideal for processing documents with monetary values, such as invoices, receipts, contracts, forms, and financial reports, where capturing accurate information is essential for automating processes.
- **High robustness for documents in the wild**:
  Our prebuilt information extractors handle challenging document conditions, including rotated images, watermarks, noise, and checkboxes, ensuring reliable performance even with imperfect or low-quality inputs.
- **Seamless integration**: Designed for enterprise applications, our extractors provide structured outputs in JSON format, making it easy to integrate into existing automation pipelines, databases, and business workflows.

## What models does Upstage provide?

### Receipt

<table>

<tbody>

<tr>

<td width="120px">Sample document</td>

<td>

<figure>

![receipt.jpg](/assets/images/docs/receipt.jpg)

<figcaption>General receipt</figcaption>

</figure>

</td>

</tr>

<tr><td>Alias</td><td>receipt-extraction</td></tr>

<tr><td>Currently points to</td><td>[receipt-extraction-3.2.0](/docs/models/history#receipt-extraction-320-deprecated)</td></tr>

<tr><td>RPS <a href="/docs/guides/rate-limits">(Learn more)</a></td><td>1</td></tr>

</tbody>

</table>

### Logistics documents

<table>

<tbody>

<tr>

<td>Sample document</td>

<td>

<figure>

![air-waybill.png](/assets/images/docs/air-waybill.png)

<figcaption>Air waybill</figcaption>

</figure>

</td>

<td>

<figure>

![billoflading.png](/assets/images/docs/bol.png)

<figcaption>Bill of lading</figcaption>

</figure>

</td>

<td>

<figure>

![shipping-request.png](/assets/images/docs/shipping-request.png)

<figcaption>Shipping request</figcaption>

</figure>

</td>

</tr>

<tr><td>Alias</td><td>air-waybill-extraction</td><td>bill-of-lading-and-shipping-request-extraction</td><td>bill-of-lading-and-shipping-request-extraction</td></tr>

<tr><td>Currently points to</td><td>[air-waybill-extraction-250415](/docs/models/history#air-waybill-extraction-250415-deprecated)</td><td>[bill-of-lading-and-shipping-request-extraction-250415](/docs/models/history#bill-of-lading-and-shipping-request-extraction-250415-deprecated)</td><td>[bill-of-lading-and-shipping-request-extraction-250415](/docs/models/history#bill-of-lading-and-shipping-request-extraction-250415-deprecated)</td></tr>

<tr><td>RPS <a href="/docs/guides/rate-limits">(Learn more)</a></td><td>1</td><td>1</td><td>1</td></tr>

<tr>

<td>Sample document</td>

<td>

<figure>

![commercial-invoice.jpg](/assets/images/docs/commercial-invoice.jpg)

<figcaption>Commercial invoice</figcaption>

</figure>

</td>

<td>

<figure>

![packing-list.png](/assets/images/docs/packing-list.png)

<figcaption>Packing list</figcaption>

</figure>

</td>

<td>

<figure>

![kr-edc.png](/assets/images/docs/kr-edc.png)

<figcaption>수출신고필증</figcaption>

</figure>

</td>

</tr>

<tr><td>Alias</td><td>commercial-invoice-and-packing-list-extraction</td><td>commercial-invoice-and-packing-list-extraction</td><td>kr-export-declaration-certificate-extraction</td></tr>

<tr><td>Currently points to</td><td>[commercial-invoice-and-packing-list-extraction-250415](/docs/models/history#commercial-invoice-and-packing-list-extraction-250415-deprecated)</td><td>[commercial-invoice-and-packing-list-extraction-250415](/docs/models/history#commercial-invoice-and-packing-list-extraction-250415-deprecated)</td><td>[kr-export-declaration-certificate-extraction-250415](/docs/models/history#kr-export-declaration-certificate-extraction-250415-deprecated)</td></tr>

<tr><td>RPS <a href="/docs/guides/rate-limits">(Learn more)</a></td><td>1</td><td>1</td><td>1</td></tr>

</tbody>

</table>

> Don’t see your document type listed?
>
> [Contact us](https://www.upstage.ai/contact-us?utm_medium=console\&utm_source=docs-pie\&utm_content=text-link)—we provide access to hundreds of private models for a wide range of document types, and offer high-precision custom model development to meet your specific business needs.

[Extract Key Information in Upstage Studio!](https://studio.upstage.ai/library?lang=ko%2Cen\&steps=parse%2Cextract\&utm_medium=console\&utm_source=docs) — Identify and structure critical data from unstructured documents — ideal for automation beyond basic parsing.

## Input requirements

- **Supported file formats:** JPEG, PNG, BMP, PDF, TIFF, HEIC, DOCX, PPTX, XLSX, HWP, HWPX
- **Maximum file size:** 50MB
- **Maximum number of pages per file:** 30 pages (For files exceeding 30 pages, the first 30 pages are processed)
- **Maximum pixels per page:** 100,000,000 pixels. For non-image files, the pixel count is determined after converting to images at a standard of 150 DPI.
- **Supported character sets:** Alphanumeric, Hangul, and Hanja are supported. Hanzi and Kanji are in beta versions, indicating that they are available but not fully supported.

> Hanja, Hanzi, and Kanji are writing systems based on Chinese characters used in Korean, Chinese, and Japanese writing systems. Despite sharing similarities, they possess distinct visual representations, pronunciations, meanings, and usage conventions within their respective linguistic contexts. For more information, see [this article](https://en.wikipedia.org/wiki/Hanja).

## Example

### Request

<figure>

![receipt.jpg](/assets/images/docs/receipt.jpg)

<figcaption>receipt.jpg</figcaption>

</figure>

_Request/response examples: prebuilt-information-extraction / request_

### Response

_Example: prebuilt-information-extraction / response-200 / default_

[Extract Key Information in Upstage Studio!](https://studio.upstage.ai/library?lang=ko%2Cen\&steps=parse%2Cextract\&utm_medium=console\&utm_source=docs) — Identify and structure critical data from unstructured documents — ideal for automation beyond basic parsing.

## Frequently Asked Questions

Check out frequently asked questions below. For more FAQs, visit the [FAQ page](/docs/resources/faq).

### Q. Can I request multiple documents at once?

We currently do not provide an interface for requesting multiple documents at once. \
We recommend sending images one at a time in series instead of sending multiple simultaneous requests. \
Sending many requests at once may result in a "429 Too Many Requests" error.

### Q. Is there an interface for filtering specific fields in the Prebuilt information extraction API response?

We do not provide an interface to filter specific fields from the API response. We recommend that you extract the necessary field from the response JSON.

```python copy
# Example for filtering "store.store_address" from the receipt extraction API reponse
response = requests.post(url, headers=headers, files=files)
data = response.json()
addresses = [field['value'] for field in data.get('fields', []) if (field['key'] == 'store.store_address' and field['type'] == 'content')]
print(addresses)
```

### Q. Why am I getting '415 Unsupported Media Type' error during an API Request?

This issue occurs when the document format is not supported.
Check supported file formats for the API being used.

### Q. Why is the response time slow or delayed?

Temporary surges in usage can cause delays; check the status page.

**Details:**

- Monthly availability is maintained at over 95% under our [Service Level Agreement](/docs/terms/sla)
- Check [status.upstage.ai](https://status.upstage.ai/) for real-time updates

### Q. How can I increase the rate limit, and are there any conditions required?

Rate limits are automatically determined by your commitment tier. \
To increase your rate limit, purchase credits to upgrade your commitment tier — you can choose a one-time purchase, or monthly or yearly auto-recharge, at the [credit purchase page](https://console.upstage.ai/billing/credit). \
For details on each tier and its rate limits, see the [rate limits page](/docs/guides/rate-limits) or [upstage.ai/pricing/api](https://www.upstage.ai/pricing/api). \
If no commitment tier covers the limits you need, [contact us](https://www.upstage.ai/contact-us?utm_medium=console\&utm_source=docs\&utm_content=faq) with your requirements.

### Q. Why am I getting '429 Too Many Requests' error during an API request (rate limit)?

Rate limits are restrictions set by our API on how frequently a user can make requests within a given time frame. \
For detailed information, please refer to the [rate limits page](/docs/guides/rate-limits). \
If you encounter 429 errors, reduce the frequency of your requests and try again after a few seconds or a minute. \
To raise the limit itself, upgrade your commitment tier by purchasing credits at the [credit purchase page](https://console.upstage.ai/billing/credit).