# Azure Retail Price Comparator – Regions & Meter Changes (`maydit/azure-retail-price-comparator`) Actor

Compare official Azure VM retail USD prices across regions with exact SKU, product, unit and reservation terms. Track saved meter changes and compute-only estimates without a key.

- **URL**: https://apify.com/maydit/azure-retail-price-comparator.md
- **Developed by:** [Brandt May](https://apify.com/maydit) (community)
- **Categories:** AI
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 60.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 saved observations

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

![Azure Retail Price Comparator — illustrative workflow](https://mayd-it.com/assets/actor-banners/azure-retail-price-comparator-b811f056b585.png)

## Azure Retail Price Comparator – Regions & Meter Changes

Compare official Azure VM retail USD prices across regions with exact SKU, product, unit and reservation terms. Track saved meter changes and compute-only estimates without a key.

### Built for a repeatable workflow

FinOps consultants, MSPs and cloud buyers comparing retail meters before quoting or choosing a region.

Prevent Windows, Spot, reservation and ordinary retail rates being blended into an inaccurate budget.

1. Choose exact VM SKUs and regions.
2. Compare only matching comparisonGroup values and read priceType, unit and reservationTerm.
3. Export planning assumptions or repeat the same snapshot to identify changed published rates.

### Start with a real sample

The default input is a small live-source check. You need no source API key or proxy. Open the dataset for records, SUMMARY for complete/partial coverage and RUN_REPORT for a readable explanation.

#### Compare standard base VM rates

Compare the exact Standard_D2s_v5 base-product consumption meter in two regions.

```json
{
  "armSkuNames": [
    "Standard_D2s_v5"
  ],
  "regions": [
    "eastus",
    "westeurope"
  ],
  "maxResults": 5
}
```

#### Read a Windows Spot meter

Read the explicitly labelled Windows Spot retail meter; no live Spot capacity is checked.

```json
{
  "armSkuNames": [
    "Standard_D2s_v5"
  ],
  "regions": [
    "eastus"
  ],
  "productVariants": [
    "windows"
  ],
  "purchaseOptions": [
    "spot"
  ],
  "maxResults": 3
}
```

#### Keep reservation terms separate

Export base-product reservation rows with their source term; no unsupported hourly conversion.

```json
{
  "armSkuNames": [
    "Standard_D2s_v5"
  ],
  "regions": [
    "eastus"
  ],
  "priceTypes": [
    "Reservation"
  ],
  "maxResults": 5
}
```

### Output and interpretation

- `title`
- `armSkuName`
- `armRegionName`
- `productVariant`
- `purchaseOption`
- `priceType`
- `reservationTerm`
- `unitOfMeasure`
- `retailPrice`
- `effectiveStartDate`
- `estimatedRetailComputeUsd`
- `retailPriceChangeUsd`
- `comparisonStatus`
- `sourceUrl`

Every row includes a stable recordId, sourceUrl, observedAt, contentHash, comparisonStatus, changedFields and the prior observation when comparison is enabled. Output retains source meaning; nullable values mean not available or not applicable. comparisonGroup isolates product/SKU/price type/term/unit/tier/currency combinations. lowestObservedRetailPrice compares only selected observed regions, never all Azure regions. effectiveStartDate and rateTiming distinguish listed effective versus announced future rates. A base product label does not guarantee a particular OS. Reservation term prices remain raw even when the source unit says1Hour.

### Monitoring without false changes

Set comparePrevious:true. The first successful complete run creates a baseline and emits new observations. onlyChanges:true enables comparison and suppresses unchanged results; a correct repeat may return zero rows. History is separated by the documented inputs, filters, snapshotName and result cap. Run a snapshot sequentially: concurrent writers are detected and a conflicting run will not overwrite history.

Only complete successful collection and confirmed dataset writes can advance history. Spending caps, output truncation, source failures, request/deadline limits or unreached inputs preserve the prior baseline. A partial dataset may contain real observations, but it is not a full check. Missing rows never establish removals. Source metadata dates are part of comparison and may change without a numeric score/price change.

### Boundaries

- USD retail list prices only; other cloud services and currencies are outside this first release.
- No negotiated bill, live inventory, deployment or savings guarantee.
- Cross-region comparisons include only successful observed selected meters; partial runs are explicitly marked.
- Only non-reservation 1 Hour meters get compute-hour arithmetic.
- maxResults is1–100; maxRunSeconds is30–120. Exact cap equal to the whole selected set can still be complete; truncation cannot.
- No credentials, arbitrary URLs, proxies or authentication bypasses. HTTP401/403/429 stops further source requests.
- This Actor calls only documented public APIs; website crawling is not performed.

### Pricing

$0.002 per confirmed saved result, plus the $0.00005 Actor-start event. Result charges are checked before each write; invalid input, failed source responses and filtered/unchanged items are never billed as result rows. Apify’s displayed pricing and run spending cap govern the run.

The Azure API is public and free. This Actor adds bounded selection, consistent output, explicit comparisons, saved change history and integrations. No free-text OData or arbitrary URLs are accepted.

### Companion workflows

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

#### [GPU Cloud Rate Monitor – Runpod & Lambda Price Changes](https://apify.com/maydit/gpu-cloud-rate-monitor)

Build a compute sourcing worksheet with Azure VM meters beside separately selected Runpod/Lambda GPU rental rates.

1. Choose the relevant GPU providers and models in the companion Actor’s own input form.
2. Keep GPU-hour rates, instance-hour meters, memory, region and reservation terms in separate columns; compare a defined workload’s total costs manually.

These are retail observations with different resource allocations. They do not establish equal performance, current capacity, negotiated costs or a cheapest provider.

#### [AI Model Price & Capability Monitor - Models.dev](https://apify.com/maydit/ai-model-price-capability-monitor)

Add model API rates when comparing a hosted inference API with a self-managed deployment budget.

1. Select the exact model/provider rates relevant to your workload in the companion tool.
2. Estimate token usage separately from VM hours, storage and network costs; retain units, source URLs and dates.

Token rates and VM-hour rates are different costs. This combination supplies inputs for your budget model; it does not calculate equivalent throughput or guarantee savings.

### Integrations and support

Use the Apify API, tasks, schedules, webhooks, CSV/JSON exports or Apify MCP with the same small input. Keep source attribution, timing and SUMMARY alongside data sent to an AI assistant. This Actor is independently maintained by Mayd It and is not endorsed by the source providers.

Source documentation: https://learn.microsoft.com/en-us/rest/api/cost-management/retail-prices/azure-retail-prices

For an issue, include the run link, small reproducible input and the relevant SUMMARY source failure. Never include secrets.

# Actor input Schema

## `armSkuNames` (type: `array`):

Exact ARM SKUs, e.g. Standard_D2s_v5. At most3; SKU × region combinations limited to6.

## `regions` (type: `array`):

Exact lowercase ARM regions, at most3. This reads published prices, not current availability.

## `priceTypes` (type: `array`):

Consumption, DevTestConsumption or Reservation. Terms stay separate; reservation price is never multiplied as an hourly charge.

## `purchaseOptions` (type: `array`):

standard, spot or low_priority. Inferred only from explicit Spot/Low Priority meter labels.

## `productVariants` (type: `array`):

base or windows. base means the published product name has no Windows marker; it is not an OS compatibility guarantee.

## `primaryMetersOnly` (type: `boolean`):

Keep isPrimaryMeterRegion:true meters. False includes other published meters, preserving the flag.

## `computeHours` (type: `integer`):

Used only for non-reservation 1 Hour meters. Hours × retail rate excludes ancillary costs; it is not a quote.

## `maxResults` (type: `integer`):

A billed result is one confirmed saved observation. Truncation prevents history advancement.

## `comparePrevious` (type: `boolean`):

The first complete run establishes history. Partial/failed/capped runs never advance it.

## `onlyChanges` (type: `boolean`):

Enables comparison. Unchanged runs may save zero rows. Source-date changes can count as changes.

## `snapshotName` (type: `string`):

1–80 letters, digits, underscores or hyphens. Inputs/filters/output cap also separate history.

## `maxRunSeconds` (type: `integer`):

Shared request/deadline budget. Source API calls are paced and access-denied responses stop remaining work.

## Actor input object example

```json
{
  "armSkuNames": [
    "Standard_D2s_v5"
  ],
  "regions": [
    "eastus",
    "westeurope"
  ],
  "priceTypes": [
    "Consumption"
  ],
  "purchaseOptions": [
    "standard"
  ],
  "productVariants": [
    "base"
  ],
  "primaryMetersOnly": true,
  "computeHours": 730,
  "maxResults": 5,
  "comparePrevious": false,
  "onlyChanges": false,
  "snapshotName": "default",
  "maxRunSeconds": 90
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `report` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "armSkuNames": [
        "Standard_D2s_v5"
    ],
    "regions": [
        "eastus",
        "westeurope"
    ],
    "priceTypes": [
        "Consumption"
    ],
    "purchaseOptions": [
        "standard"
    ],
    "productVariants": [
        "base"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("maydit/azure-retail-price-comparator").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "armSkuNames": ["Standard_D2s_v5"],
    "regions": [
        "eastus",
        "westeurope",
    ],
    "priceTypes": ["Consumption"],
    "purchaseOptions": ["standard"],
    "productVariants": ["base"],
}

# Run the Actor and wait for it to finish
run = client.actor("maydit/azure-retail-price-comparator").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "armSkuNames": [
    "Standard_D2s_v5"
  ],
  "regions": [
    "eastus",
    "westeurope"
  ],
  "priceTypes": [
    "Consumption"
  ],
  "purchaseOptions": [
    "standard"
  ],
  "productVariants": [
    "base"
  ]
}' |
apify call maydit/azure-retail-price-comparator --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,maydit/azure-retail-price-comparator"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/yThh4F641Q2MeSHZW/builds/hRiqzyZjItoL1H34J/openapi.json
