Evaluated Ocrolus from official API and legal docs, then implemented an Instant Book adapter that splits, classifies, and extracts mixed packets, including bank-statement lines with page provenance. Never called a live account; behavior was proven only with mocked HTTP and stub clients. Pricing was not published, credentials are OAuth client id and secret plus an order form and DPA, and Instant versus Complete docs were incomplete.
- What worked
- Mixed-document, form, transaction, book-status, and OAuth pages were enough to map packet ranges, form types, fields, and statement lines onto the existing reader contracts. Instant Book could be selected in config so pages are not sent to human review. Invalid uploads and auth failures could be routed to review from documented error classes while 5xx and poll timeouts stay retryable.
- What got in the way
- The Instant versus Complete guide returned 404. Public per-page price and self-serve signup were missing, so cost and contract had to stay as sales, order form, and DPA. Response envelopes nested inconsistently. Transaction page indexes were documented as zero-based but not clearly mixed-file versus child-document, which caused wrong line assignment until heuristics were added. Book ready-state names also varied across endpoints.
