Hirak OCR API

Name: Hirak OCR API API
Brand: Hirak OCR API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLVisionapiKey2 EndpointsREST

For Agents

Extract text from images in 100+ languages with POST /ocr and discover supported languages via GET /languages. Authenticated with an X-API-Key header.

Quickstart

Get started with Hirak OCR API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"extract text from an image"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Hirak OCR API API.

Extract text from an image with POST /ocr supporting more than 100 languages

Enumerate supported OCR languages with GET /languages before submitting

Read printed text from receipts, signs, and document scans

Pre-process images upstream to improve OCR accuracy on low-contrast inputs

GET STARTED

Start building with Hirak OCR API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Hirak OCR API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Hirak OCR API, keeping it validated and agent-ready. Hirak OCR extracts text from images using optical character recognition with support for more than 100 languages. The two-endpoint surface — POST /ocr to extract text and GET /languages to list supported languages — is authenticated with an X-API-Key header and is suitable for receipt parsing, document digitisation prototypes, and lightweight in-app text extraction. The API is intentionally small, so integration is fast and most engineering effort goes into pre-processing the input image.

Use Cases

Patterns agents use Hirak OCR API API for, with concrete tasks.

★ Receipt Capture for Expense Tools

Expense apps let users photograph a receipt and capture line items without typing. POST /ocr returns the extracted text in the chosen language so a downstream parser can pick out date, total, and merchant. The 100+ language support covers most travel scenarios without switching providers.

When the user uploads a receipt photo, call POST /ocr with language=en and pass the returned text to a line-item parser to populate the expense form.

Multilingual Document Digitisation

Teams digitising legacy documents in mixed languages need an OCR engine that supports the right scripts. /languages returns the list of supported languages so an agent can confirm coverage, and /ocr accepts a language parameter so the engine can be tuned per page.

First call GET /languages to confirm support for ja, then run POST /ocr with language=ja against each scanned page of a Japanese contract.

In-App Text Lift from Screenshots

Productivity apps offer 'copy text from this screenshot' features. Hirak OCR's POST /ocr returns the text quickly enough to feel interactive in a desktop app, and the small API surface keeps the integration light.

When the user clicks 'extract text' on a screenshot, send the image to POST /ocr with language=auto and return the recognised text to the clipboard.

AI Agent Document Reader

An AI assistant reads a user-supplied image and answers questions about its content. Through Jentic, the agent searches for the OCR operation, loads the schema, and executes POST /ocr with the user's vault-stored X-API-Key. The extracted text is then summarised by the agent's LLM.

When the user uploads a photo of a flyer, search Jentic for 'extract text from image', execute POST /ocr, and summarise the result for the user.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for hirak ocr api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/ocr

Extract text from an image

GET

/languages

List supported OCR languages

POST

/ocr

Extract text from an image

GET

/languages

List supported OCR languages

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Hirak OCR X-API-Key is stored encrypted in the Jentic vault (MAXsystem). The agent receives a scoped execution token, and Jentic injects the X-API-Key header at call time so the raw key never enters the model context.

Intent-based discovery

Agents search by intent (e.g., 'extract text from image') and Jentic returns the POST /ocr operation with its body schema, so the agent submits the image and language without reading docs.

Time to first call

Direct Hirak OCR integration: a few hours to wire image upload, language selection, and error handling. Through Jentic: under 20 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Mindee API

Document understanding API that goes beyond raw OCR to structured field extraction.

Choose Mindee when the user needs structured fields like total or invoice number; use Hirak OCR for raw text extraction.

Complementary

OpenAI API

GPT-4 vision can interpret OCR output or directly read images for downstream reasoning.

Use OpenAI to summarise or classify Hirak OCR output, or for vision tasks where structured text is not the goal.

Complementary

Abstract API

Bundle of utility APIs that pair with Hirak OCR for downstream validation of extracted text.

Use Abstract API alongside Hirak OCR when extracted text needs follow-up validation such as VAT number checks.

FAQs

Specific to using Hirak OCR API API through Jentic.

Why is there no official OpenAPI spec for Hirak OCR API?

Hirak does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Hirak OCR API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

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 the MAXsystem vault 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.