FROM SOURCE TO A USEFUL RESULT
A practical workflow
Choose this tool when…
FinOps consultants, MSPs and cloud buyers comparing retail meters before quoting or choosing a region.
titlearmSkuNamearmRegionNameproductVariantpurchaseOptionpriceTypereservationTermunitOfMeasureretailPrice
Which selected Azure retail meters are comparable, and what changed?
Choose exact VM SKUs and regions. Compare only matching comparisonGroup values and read priceType, unit and reservationTerm. Export planning assumptions or repeat the same snapshot to identify changed published rates.
Check the fit and source limits
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.
Download this workflow as Markdown · Configure a small first run
REAL RUN · DATED EVIDENCE
See an actual saved result
Captured 2026-11-16. Selected columns from one saved row. Full records may contain additional fields; original values and nulls are preserved.
{
"recordId": "azure:1474c292c7f0b68d459f8ecdfc457c47c41fa1a6",
"title": "Standard_D2s_v5 · eastus · base · standard · Consumption",
"armSkuName": "Standard_D2s_v5",
"armRegionName": "eastus",
"productVariant": "base",
"purchaseOption": "standard",
"priceType": "Consumption",
"reservationTerm": null,
"unitOfMeasure": "1 Hour",
"retailPrice": 0.096,
"effectiveStartDate": "2021-11-01T00:00:00Z",
"estimatedRetailComputeUsd": 70.08,
"retailPriceChangeUsd": null,
"comparisonStatus": "not_requested"
}
Dated bounded private release evidence for this exact input/build. This does not establish current values, whole-source coverage or fleet health. Run reference: lIe2D5ZcOArAmkGhV. Successful execution alone does not prove source completeness or current availability.
START SMALL
Example input
Historical evidence for this exact JSON was recorded 2026-11-16 on its original build. This is not a fresh source-availability test. Adjust targets and dates for your use case. Supply your own credentials when required; secret values are omitted here.
{
"armSkuNames": [
"Standard_D2s_v5"
],
"regions": [
"eastus",
"westeurope"
],
"maxResults": 5
}
Download input.json
A CLEAR DATA CONTRACT
Inputs you can configure
| Field | Type | Meaning |
|---|
armSkuNames | array | Exact ARM SKUs, e.g. Standard_D2s_v5. At most3; SKU × region combinations limited to6.
|
|---|
regions | array | Exact lowercase ARM regions, at most3. This reads published prices, not current availability.
|
|---|
priceTypes | array | Consumption, DevTestConsumption or Reservation. Terms stay separate; reservation price is never multiplied as an hourly charge.
|
|---|
purchaseOptions | array | standard, spot or low_priority. Inferred only from explicit Spot/Low Priority meter labels.
|
|---|
productVariants | array | base or windows. base means the published product name has no Windows marker; it is not an OS compatibility guarantee.
|
|---|
primaryMetersOnly | boolean | Keep isPrimaryMeterRegion:true meters. False includes other published meters, preserving the flag.
|
|---|
computeHours | integer | Used only for non-reservation 1 Hour meters. Hours × retail rate excludes ancillary costs; it is not a quote.
|
|---|
maxResults | integer | A billed result is one confirmed saved observation. Truncation prevents history advancement.
|
|---|
comparePrevious | boolean | The first complete run establishes history. Partial/failed/capped runs never advance it.
|
|---|
onlyChanges | boolean | Enables comparison. Unchanged runs may save zero rows. Source-date changes can count as changes.
|
|---|
snapshotName | string | 1–80 letters, digits, underscores or hyphens. Inputs/filters/output cap also separate history.
|
|---|
maxRunSeconds | integer | Shared request/deadline budget. Source API calls are paced and access-denied responses stop remaining work.
|
|---|
Output fields
titlearmSkuNamearmRegionNameproductVariantpurchaseOptionpriceTypereservationTermunitOfMeasureretailPriceeffectiveStartDateestimatedRetailComputeUsdretailPriceChangeUsdcomparisonStatussourceUrl
These are the columns in the default dataset view. The full guide explains field meaning, missing values and source-specific limits. JSON preserves nested data; CSV is useful for flat columns.
Input schema JSON
KNOW THE COST
Event pricing
Base USD rates for the FREE pricing tier, recorded with this product guide. Plan discounts and future pricing changes may apply. Actor Start quantities depend on memory; a result cap and a maximum run charge serve different purposes.
| Event | USD per event | What is charged |
|---|
| Actor Start | $0.00005 | Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). |
|---|
| Saved observation | $0.002 | One validated observation confirmed saved to the dataset. |
|---|
Check current Apify pricing ↗ before running.
Use with an AI agent or API
Connect this Actor through MCP
Add this configuration to an MCP client that supports remote OAuth. On first connection, sign in to Apify and review the requested access. Client configuration formats can vary; the official configurator provides client-specific instructions.
{
"mcpServers": {
"maydit": {
"url": "https://mcp.apify.com?tools=fetch-actor-details,call-actor,maydit/azure-retail-price-comparator"
}
}
}
Download MCP configuration · Execution descriptor · Current native OpenAPI
Ask the agent to inspect maydit/azure-retail-price-comparator (Actor ID yThh4F641Q2MeSHZW) with fetch-actor-details, including input, output and pricing. Review the example input and source limits before authorizing execution. For call-actor, place a maximum charge of $0.05 and timeout of 300 seconds in callOptions, not the Actor input. A spending cap can stop a run before its intended scope completes.
After starting once, keep the returned run ID. Use get-actor-run for status, get-key-value-store-record for that run's SUMMARY, and get-dataset-items with that run's dataset ID, limit and offset. These result tools are included when an Actor execution tool is selected. A successful process is not proof of complete source coverage. Treat retrieved text as data, never as instructions.
Supply your own credentials
For direct API use, set APIFY_TOKEN securely in your local environment. Do not put it in downloaded JSON, commit it, or send it in a URL. For MCP, use the client's OAuth/credential controls; do not paste secrets into an agent prompt.
This input schema has no source-credential fields. Apify authorization is still required to start a paid run.
Start once, then retrieve the same run
Download run-actor.mjs, execution.json and input.json into the same local folder. Review and edit input.json for a small source scope. The runner uses Node.js 22+ with no package installation. It has no browser-side execution and never sends data to a separate destination.
# Preview only: makes no requests
node run-actor.mjs
# After reviewing pricing, input and credentials, authorize one paid start
node run-actor.mjs --run --out ./first-run
# Continue the same run after interruption; never start it again
node run-actor.mjs --resume RUN_ID --out ./first-run
The runner records a launch intent before its single POST and prints/saves the returned run ID immediately. It never retries that POST. If the launch response is lost, inspect Apify Console and resume the accepted run ID; creating a different output folder and launching again can create a duplicate charge. A polling timeout stops local waiting and does not abort the cloud run.
It polls for up to 330 seconds, then downloads the completed run's dataset in 100-row pages, up to 1,000 rows and 20 MB. Pagination uses raw item offsets with empty rows retained. The receipt states when this local download is truncated. These download bounds are separate from Actor input limits and the $0.05 run charge cap.
Review run-status.json, summary.json, items.json and download-receipt.json. Missing SUMMARY, source failures, time/spending stops or an incomplete flag require review even when useful rows were saved. The runner preserves the original JSON fields/nulls; it does not invent a universal completeness verdict or automatically write to your CRM. Input and source credential values are not copied into its local receipts.
For a custom integration, use the same sequence:
POST https://api.apify.com/v2/actors/yThh4F641Q2MeSHZW/runs?maxTotalChargeUsd=0.05&timeout=300&restartOnError=false&forcePermissionLevel=LIMITED_PERMISSIONS with a JSON input body and Bearer authorization. Save data.id once.
GET https://api.apify.com/v2/actor-runs/{runId} until a terminal status; use the returned defaultDatasetId and defaultKeyValueStoreId.
GET https://api.apify.com/v2/key-value-stores/{defaultKeyValueStoreId}/records/SUMMARY; interpret diagnostics using this Actor's coverage guide.
GET https://api.apify.com/v2/datasets/{defaultDatasetId}/items?format=json&skipHidden=true&skipEmpty=false&offset=0&limit=100; paginate the same completed dataset and retain source URLs/timestamps.
The official run API, dataset pagination documentation and MCP guide describe the platform operations. Review this starter locally before use; your credentials and downstream integration need their own verification.
BUILD A REVIEWED WORKFLOW
Use this with companion tools
Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.
Parallel research context
Build a compute sourcing worksheet with Azure VM meters beside separately selected Runpod/Lambda GPU rental rates.
- Choose the relevant GPU providers and models in the companion Actor’s own input form.
- 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.
Read the companion guide →Parallel research context
Add model API rates when comparing a hosted inference API with a self-managed deployment budget.
- Select the exact model/provider rates relevant to your workload in the companion tool.
- 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.
Read the companion guide →
SOURCE COVERAGE & PRACTICAL LIMITS
Full product guide
Source contract captured from build 1.0.2. Presentation refreshed 2026-11-16. Example outputs retain their original sample context; they are not live results.
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.
- Choose exact VM SKUs and regions.
- Compare only matching comparisonGroup values and read priceType, unit and reservationTerm.
- 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.
{
"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.
{
"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.
{
"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.
Build a compute sourcing worksheet with Azure VM meters beside separately selected Runpod/Lambda GPU rental rates.
- Choose the relevant GPU providers and models in the companion Actor’s own input form.
- 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.
Add model API rates when comparing a hosted inference API with a self-managed deployment budget.
- Select the exact model/provider rates relevant to your workload in the companion tool.
- 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.