OCR Web Service
for LuumenAI

Run OCR jobs and check page quota without leaving the terminal

Hand a document to OCR Web Service and get the recognized text back in your session. Ask what plan the account is on, how many pages are left, and when it expires. Pull processing logs for a date range when a job looks wrong. Luumen connects over basic auth, and every tool here is read-only.

The OCR Web Service toolbox

4 tools, all read-only. They answer instantly, and every call is logged.

  • ReadGet Account CredentialsExtract OCRWebService credentials (user_name, license_code) from connection metadata.
  • ReadGet Account InformationRetrieve OCRWebService account information including remaining pages, subscription plan, and expiration date.
  • ReadOCR Web Service LogRetrieve OCR processing logs for a date range on your account.
  • ReadOCRWebService RecognizeCall SOAP Recognize operation.

Questions

How does LuumenAI connect to OCR Web Service?

Authorize once with Basic auth. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in OCR Web Service on its own?

No. Every one of the 4 tools LuumenAI has for OCR Web Service is read-only, so it can answer questions from OCR Web Service but cannot change anything in it. Reads are not gated — they answer immediately, and each one is recorded on the audit trail with the actor and the result.

Who gets access to the integration?

You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.

Is there an audit trail?

Every call to OCR Web Service is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put OCR Web Service to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.