Setting the file. One moment.
Subchapter 2.6
references/pricing-estimate.mdMarkdown2 KBView on GitHub
get_retail_prices. Compare options with separate calls when needed.
Preserve productName, skuName, armSkuName, price type, unit, region,
and currency so the selected row is auditable. The tool requests up to 5000
rows. If Count reaches that limit or NextPageLink is present, narrow the
filters and disclose that the result set was truncated; do not invoke the
returned URL directly.productName, skuName, armSkuName, meter name, and price type. Never
silently choose among multiple meter shapes.unit price x usage = estimated period cost and list every assumption.
Reservation prices are term purchase totals; normalize one-year prices by 12
and three-year prices by 36. Savings Plan and consumption prices are hourly
meter rates and may be multiplied by expected hours.start_pricesheet_download, then poll get_pricesheet_status using its
retry interval. Label retail and negotiated values separately.
If a pricing operation is unavailable, use the mapped API from
tool fallback.Retail estimates are not bills or realized savings. If the user provides an
existing scope and wants current spend, hand off to cost-analysis.