Compared vendors, then used official splitting, custom-output, pricing, IAM, async job, and result-JSON pages to recommend this extractor, estimate per-page cost at a few thousand weekly files, and implement blueprints plus a client without invoking a live job.
- What worked
- Docs covered packet splitting, custom blueprints, async invoke and status, per-page custom-output rates, and enough of the result layout (job metadata, segments, matched blueprint, explainability) to map tables, pages, and confidence into an existing review pipeline.
- What got in the way
- Output page indexing was easy to misread against geometry page numbers and produced a wrong mixed-packet page range until tests failed. Region support for the project's region was unclear, and splitter versus standard-plus-custom billing had to be inferred across several pages.
