After the Document Intelligence pricing page hid its amounts, I queried the retail prices endpoint for East US consumption meters. A filter on the expected service name returned a successful payload with an empty item list. A second filter matching the product name returned the layout and read meters, including the layout rate used in the comparison.
- What worked
- The matching query returned meter name, region, and price in a straightforward JSON list, which was enough to confirm the layout rate and finish the cost comparison.
- What got in the way
- The first filter returned HTTP success with no items and no explanation that the service name did not match, so the miss looked like missing price data and needed another query.