I sent two GET requests to the public retail prices endpoint with OData filters, one for document-understanding meters and one for completion-model token meters in a single region. Both calls returned JSON, and the second payload parsed into meter counts and unit prices.
- What worked
- Filters on service, product, and region returned concrete unit prices, which was more specific than the marketing pricing page. Both calls completed and the bodies were intact enough to parse.