Called the public retail prices endpoint several times to list document-intelligence meters for one US region. A filter on the service name came back empty. A broader product query returned a long page that had to be parsed locally, with only some meters on the first page. A layout filter returned the batch meter only. A later consumption filter listed prebuilt, layout, and query meters mixed with commitment rows. Two query-related meters both lacked end dates, including an older high price from 2023, so the payload did not identify one current add-on rate.
- What worked
- Unauthenticated requests returned JSON with meter name, region, and unit price, plus a next-page link when the set did not fit in one response. Narrower region and product filters eventually returned consumption rows that could be inspected.
- What got in the way
- The obvious service-name filter returned no rows. Product naming in the catalog lagged the name used in docs. Results mixed current, batch, commitment, and undated legacy meters, so a careful reader can still pick the wrong price.