# Barcode reader

Read EAN, UPC, Code 128, Code 39, ITF and other barcodes from a picture, with the type and position of each.

Looks for one-dimensional barcodes in the picture and returns the text, type and position of each. If nothing is found at first, it tries again with an enlarged copy and with the colours inverted.

- Endpoint: `POST https://setget.net/v1/tools/barcode-decode` with JSON `{"input": {...}}` (add `"wait": 30` to hold the reply until the job finishes)
- MCP: `run_tool` with `slug` = `barcode-decode`
- Page: https://setget.net/tools/barcode-decode

## Files in, files out

This is a file tool. Its file inputs take file references, not file contents and not web addresses.

- Get a reference by uploading: `curl -T FILE https://setget.net/drop/` prints a line `ref  <id>/f1`. Or `POST https://setget.net/v1/drops` with `{"files":[{"name","size"}]}`, PUT the bytes to the returned `upload.url` with the listed headers, and use the file's `ref`. Over MCP use the `drop` tool. A file under about 700 KB can also be sent in place as a `data:<type>;base64,<content>` URI.
- Uploads are at most 100 MB per file, are readable by anyone with the link, and expire (one hour by default). Programs are refused.
- The tool runs as a job. The reply is `{"tool", "ms", "result", "files", "job"}`: `result` is JSON, and every result file comes back in `files` as `{"name", "size", "content_type", "kind", "url", "ref"}`. Download it from `url`, or pass `ref` as the input of another file tool.
- A job still running when the wait ends answers 202 with `job`. Follow it with `GET https://setget.net/v1/jobs/<id>?wait=30`, or stream progress from `GET https://setget.net/v1/jobs/<id>/events` (over MCP: the `job` tool). A person can watch it at `job.url`.

## Inputs

- `image` (required, file, a file reference such as `DROP_ID/f1`, accepts image): A picture that shows one or more barcodes.
- `types` (optional, array): Only look for these types: ean13, ean8, upca, upce, isbn13, isbn10, code128, code39, code93, codabar, itf, databar, databar-expanded. Leave empty to look for all of them.

## Example 1: Read an EAN-13 product barcode

Upload first. Each placeholder below stands for the reference of one upload: `DROP_ID/f1` = [sample-barcode.png](https://setget.net/static/samples/sample-barcode.png).

```json
{"input":{"image":"DROP_ID/f1"},"wait":30}
```

## Example 2: Look for retail barcodes only

Upload first. Each placeholder below stands for the reference of one upload: `DROP_ID/f1` = [sample-barcode.png](https://setget.net/static/samples/sample-barcode.png).

```json
{"input":{"image":"DROP_ID/f1","types":["ean13","upca"]},"wait":30}
```

**Which barcodes can it read?** EAN-13, EAN-8, UPC-A, UPC-E, ISBN-10 and ISBN-13, Code 128, Code 39, Code 93, Codabar, ITF (Interleaved 2 of 5) and GS1 DataBar. For QR codes use qr-decode.

**Why does my product barcode come back as ISBN-13?** Book numbers are EAN-13 barcodes that start with 978 or 979, so they are reported as ISBN-13. Set "types" to ean13 to have them reported as EAN-13.

**Is the check digit included?** Yes. EAN and UPC results are the full number as printed under the bars, with the check digit, which has already been verified.

**Why was no barcode found?** The bars are usually too thin in the picture, blurred, or at an angle. Crop closer, use a sharper or larger picture, and turn it so the bars run straight across.

**What do the position numbers mean?** They are pixels in the picture as a viewer shows it, measured from the top left corner: the box around the bars that were read.
