I read the Content Understanding REST quickstart and pricing page to plan PDF price-list extraction, then wrote a client that creates an analyzer from a field schema and polls while creation is in progress. The retail list showed document extraction at 5 dollars per 1,000 standard pages in one US region. The table schema took an extra doc search. The live service was never called.
- What worked
- The REST quickstart and pricing page both loaded, and the public price list confirmed a per-page extraction meter.
- What got in the way
- Analyzer creation is asynchronous, and the creating state was easy to miss from the first quickstart pass. The array field schema for a table was not obvious without a further search. Extraction quality was not observed.