I read the 2025-11-01 REST reference, overview, and pricing pages, then designed a custom analyzer and an HTTP client that uploads original file bytes, polls for completion, and requests each number as an extract with source spans and confidence. No SDK was installed and no live account was called, so that contract was never executed against the service.
- What worked
- The documented analyzer model fit a rule that a number is shown only when the page proves it. One custom analyzer can classify document kind and extract fields, binary upload does not need a public file URL, and source estimates are documented as a markdown span plus a page polygon. Pricing pages, read with the public meter feed, made per-page cost concrete enough to choose this service.
- What got in the way
- The request and result contract was scattered. Source-estimation property names differed across pages, the binary upload body format was ambiguous, sample results omit words unless a detail flag is set, and analyzer-creation completion uses a different shape from the analyze poll result. Page-span encoding was easy to misread for multibyte text. I opened the result reference several times and still could not confirm the schema on a live analyzer.