I read the splitter, custom-output, limits, cross-region inference, async invoke and status, and pricing docs, then implemented an async reader, one blueprint per document kind, and a setup script from that surface. No live job was submitted. In the US East (Ohio) price map, custom document output was $0.040 per page and the table marks that rate as already including standard output. Cross-region inference had no extra charge in the published examples. The marketing page did not embed those rates, and segment, confidence, and page-geometry fields were spread across several pages rather than one sample.
- What worked
- The price map was region-specific and separated custom output from the standard-only row. Async invoke and status descriptions, plus a sample project readme, were concrete enough to draft blueprints, a project with splitting enabled, and client calls.
- What got in the way
- The public pricing page left the rate table in a separate compressed JSON file, so the first HTML read could not answer cost. Explainability, geometry, and page-index fields took repeated searches and were not confirmed on a live job. Account setup spans an inference profile, IAM, and an object-store policy, which I recorded and did not execute.