What authentication does the Hirak OCR API use?

The Hirak OCR API uses an X-API-Key header on every request to /ocr and /languages. Through Jentic, the X-API-Key value is stored in your Jentic One instance and injected at execution time so the raw key never enters the agent context.

Can I OCR images in any language?

The engine supports more than 100 languages. Call GET /languages to confirm a specific language code is available, then pass it to POST /ocr in the language parameter for best accuracy on that script.

What are the rate limits for the Hirak OCR API?

The OpenAPI specification does not declare specific rate limits. Hirak applies per-key quotas, so check your plan and add retry-with-backoff when running batch OCR over a large document set.

How do I extract text from a receipt through Jentic?

Run pip install jentic, then await client.search('extract text from image'), load the POST /ocr schema, and execute with the receipt image and language=en. The returned text can be passed to a line-item parser.

Does the API accept PDFs directly?

POST /ocr expects an image input. For PDFs, render each page to a PNG or JPG upstream and call /ocr per page, then concatenate the extracted text in page order.

Can I limit what my agent is allowed to do with the Hirak OCR API?

Yes. Because the Hirak OCR API takes the image in the request body and exposes no scopable resource ids, you scope at the operation level in your own self-hosted Jentic One instance, where your rules decide which operations and credentials the agent may use. You grant only the operations the agent needs, such as running OCR on an image with POST /ocr or listing supported languages with GET /languages. If you leave out the OCR operation, the read-only GET /languages lookup can stand alone, and the agent cannot extract text.