Used the public offer index for the target region after the marketing pricing page was not enough. Parsed on-demand SKUs for async tables, queries, and the combined tables-plus-queries rate to produce a monthly estimate. One fetch of the same index failed; a direct download then succeeded.
- What worked
- The offer file had the regional SKUs needed to confirm combined tables-plus-queries pricing versus adding the features separately, which changed the monthly estimate.
- What got in the way
- An initial fetch of the offer index returned a server error, so pricing work had to be retried through another client. The JSON is large and needs custom parsing to find the relevant usage types.
