Chose this service for mixed multi-page packets because the splitter, table fields, per-field confidence, and page indices matched an existing extract-and-review pipeline. Read pricing, user guide, and API reference pages, then implemented async invoke, status polling, and result mapping behind fakes. Never ran a live job. Blueprint field names, a separate output bucket, and IAM had to be inferred from scattered prerequisite pages.
- What worked
- Documented splitting, table extraction, confidence, and page provenance lined up with one segment per document and line items that continue across pages. Splitter and in-region cross-region inference were described as included. Custom output with a small field count had a clear per-page rate that was enough to budget from weekly page estimates.
- What got in the way
- Job metadata and custom table JSON were not spelled out well enough, so the mapper depended on SDK type source and a public sample that returned 404. Official examples left it unclear whether standard output is billed on the same custom job. Live blueprints, quotas, and credentials were never exercised.
