For AI agents: price one workload on Azure, AWS and Google Cloud

Cloud Pricing Calculators prices nothing itself. It forwards a plain-language request to the engines of the three sister calculators and returns their quotes, one per cloud. Agents can use it three ways: compose an AI link, call the API, or use the MCP server.

If your user wants a quote they can open, compare, export and share, compose a link and put it in your reply. The grammar, limits and every service slug are on the AI links page; /ai-link.json has the same as data.

2. The federation API

The OpenAPI 3.1 document is https://cloudpricingcalculators.com/openapi.json. The API is same-origin under /api/*; nothing is ever held open:

  1. POST /api/quote with {"provider": "azure" | "aws" | "gcp" | "all", "request": "…", "quoteName": "…"} (or "providers": ["azure", "gcp"] for two clouds). The request is 12 to 1000 characters of plain language. The answer is 202 with a jobId or groupId, a pollUrl and pollAfterSeconds.
  2. Poll the pollUrl (GET /api/jobs/{id} or GET /api/groups/{id}) no faster than Retry-After. Status is queued, running, complete, needs_more_detail, rate_limited or failed. Each cloud in a group succeeds or fails on its own.
  3. Optionally POST /api/groups/{id}/share to get one link holding every finished quote, laid out as a comparison. Links made this way last 7 days.

Jobs and groups can be read only by whoever created them: keep the cpc_sid cookie the first answer sets, or call from the same IP address, or use the same agent key. Anyone else gets 404. GET /api/limits shows your remaining allowance at no cost.

Access and keys

The API works without a key, on the small per-IP allowance below. For more, an X-Agent-Key header is issued on request: email w7carrington@gmail.com with what your agent does and the volume you expect. Keys are stored only as SHA-256 hashes, and an unknown key is ignored (you are treated as an unsigned caller).

Limits

WhatDefault
Builds without a key or sign-in6 per IP address per UTC day ("All three" counts 3)
Builds with an X-Agent-Key100 per key per UTC day
Builds when signed in on the site60 per user per UTC day
Imports (GET /api/import)60 per IP address per UTC day
Share links created30 per IP address per UTC day
Whole site, per cloud250 or 500 builds per UTC day, depending on the engine connection
Whole site, estimated engine spenda daily ceiling across all clouds

These are defaults and may change; GET /api/limits returns what applies to you. Over a limit the API answers 429 {"error": "rate_limited", "scope", "limit", "retryAfterSeconds", "message"}. When the site-wide spend ceiling is reached, or the store or an engine is unavailable, it answers 503 with spend_ceiling, store_unavailable or upstream_unavailable, and refuses rather than guessing.

Every build spends a daily allowance at the sister engine, so build once and reuse the result. Never put personal data, customer names or anything confidential in a request.

3. The MCP server

One MCP server covers all three clouds: https://mcp.azure-price-calculator.com/mcp (Streamable HTTP). Its tools are build_cloud_quote, get_cloud_quote, compose_quote_link and list_calculator_capabilities.

compare_cloud_quote(request, providers[], quoteName?) prices one request on several clouds through this site's API and returns one Cloud Pricing Calculators share link holding every quote, the per-cloud totals and the reason for any cloud that was skipped. It arrives with the MCP server update that adds it; if list_calculator_capabilities does not list it yet, call the API above directly.

Documents for agents

Sister calculators

To price on one cloud only, the sister calculators have their own agent endpoints and AI links:

Estimates are informational; each engine prices from its provider's published prices. See the Terms of Use and the Privacy Statement.