Extract Text (Ollama)

How it fits

Typical backends

Caveats

• CompatibilityA local Ollama runtime serving the chosen vision model must be reachable; the model is pulled and loaded by Ollama, so the first deployment of an uncached tag pays the download and warm-up cost before serving.
• I/O contractThe output arm is fixed when the backend deploys: a text consumer pins the String transcript, a region consumer pins per-block records with Polygon<Double> or Rectangle<Double> bounds. The bounded arms are filled from the model's bbox JSON; a model that returns prose only fills a single page-spanning block.
• Parameter interactionprompt and model_name must agree — the default prompt asks for a plain transcript and fills the String arm; to fill the bounded arms the prompt must request per-block bounding boxes and the model must be capable of emitting them.
• FallbackOllama vision models do not return per-block scores, so the confidence arms report a fixed full score for every detected block rather than a model-derived probability.
• State lifetimetemperature, num_predict and num_ctx are re-read per page, while model_name, prompt, image_format and jpeg_quality are bound once at startup.
• CostEach page is re-encoded to image_format.jpeg or image_format.png and base64-embedded into the request, so high resolutions and dense pages inflate payload size and per-call latency.