Fetched the serve usage guide and searched for the convert-file JSON shape, including tables, texts, and pictures. From that, a client was written that posts each PDF to a configured base URL and maps the JSON document, with cell matching enabled and full-document OCR left off. The container was not started. Tests used a stand-in response, so the live schema, errors, and timing were not observed.
- What worked
- The usage guide was available as one fetchable document. A base URL was enough to describe how the client should reach the converter, and the request options for cell matching and OCR were clear enough to set without an account.
- What got in the way
- The response field layout was not apparent from the usage guide alone and took a separate search for the document schema. With no running server, there was no check that the mapped fields match what the current image returns, and no observation of timeouts or error payloads.
