# EOL Watch > Cloud retirements, end of support dates and IaC breaking changes in one timeline. How to read this site from an agent or a script: - Every item, service, provider, cloud and category page has a Markdown form and a JSON form: add `.md` or `.json` to the address of the page, as in `/items/.md`, `/services//.md` and `/providers/.md`. The home page is `/index.md` and `/index.json`. - An address that ends in `.md` or `.json` always answers that form. The address of the page itself also answers Markdown or JSON when the `Accept` header asks for `text/markdown` or `application/json`, but a cache that already holds the HTML of that address (a browser that loaded the page, a proxy in front of the site) may answer with the HTML. - To ask with filters, add query parameters to `/data/items.json`: [Azure retirements due in the next 90 days](https://eolwatch.dev/data/items.json?cloud=azure&type=retirement&within_days=90), [what ended in the last 30 days](https://eolwatch.dev/data/items.json?within_days=30&status=ended). The answer is one page of compact rows and says for which UTC day it counted (`as_of`), how many items match (`total`) and where the next page is (`next_url`). A value that is not allowed answers 400 and names the parameter and what it accepts. - Every answer that counts days says for which UTC day it counted (`as_of`). A list can be kept for an hour or longer before it is rebuilt, so check `as_of`: when it is not today, ask `/data/items.json` with filters for the counts of today. - MCP clients connect to `https://eolwatch.dev/mcp` (Streamable HTTP, POST, no key). Its tools are `search_items`, `get_item`, `list_services`, `list_providers`, `get_provider_changes` and `recent_changes`. - In JSON a value the source does not give is null. Do not estimate it. `effective_precision` says how exact `effective_date` is: day, month, quarter or year. A month, a quarter or a year is a period, not a day, and `effective_date` then holds the first day of that period. - A retirement or an end of support ends. A breaking change takes effect: once its date has passed its `state` is `in_effect` (ask for it with `status=in_effect`) and it is never listed as ended. - The estate check runs in the reader's browser. No address of this site takes a file, a resource ID or a subscription ID. Sources policy: - Most items come from an official source: a page, feed or release note published by the vendor or the project that owns the product. Some version dates come from endoflife.date, a community project. For a few products it is the only source, and the item says so. - Every item links its source and shows the date the source was last checked. - The description of each item is drafted with AI assistance from the text of its source, checked against that source and approved by a person before it is published. The About page explains the method. - A value the vendor does not state is marked as such ("Not stated by vendor", "Date not announced"); it is never estimated. For an item tracked through endoflife.date alone, the label reads "Not stated in the source". - A date given as a month, quarter or year is shown with that precision, not as an exact day. ## Lists - [Timeline](https://eolwatch.dev/index.md): what is due in the next 90 days, soonest first. - [Azure](https://eolwatch.dev/cloud/azure.md): upcoming items for Microsoft Azure, soonest first. - [AWS](https://eolwatch.dev/cloud/aws.md): upcoming items for Amazon Web Services, soonest first. - [GCP](https://eolwatch.dev/cloud/gcp.md): upcoming items for Google Cloud, soonest first. - [OCI](https://eolwatch.dev/cloud/oci.md): upcoming items for Oracle Cloud Infrastructure, soonest first. - [Services](https://eolwatch.dev/categories/services.md): whole cloud services that are being retired. - [Features](https://eolwatch.dev/categories/features.md): features and capabilities being retired inside services that continue to run. - [Kubernetes](https://eolwatch.dev/categories/kubernetes.md): managed Kubernetes version end of support dates (AKS, EKS, GKE) and AKS platform-initiated upgrades. - [Runtimes](https://eolwatch.dev/categories/runtimes.md): language runtimes and application stacks reaching end of support. - [Databases](https://eolwatch.dev/categories/databases.md): managed database engine versions reaching end of support. - [Compute SKUs](https://eolwatch.dev/categories/compute-skus.md): virtual machine series and sizes being retired. - [OS images](https://eolwatch.dev/categories/os-images.md): operating system and machine images reaching end of support. - [APIs and SDKs](https://eolwatch.dev/categories/apis-sdks.md): API versions and SDKs being retired. - [Infrastructure as code](https://eolwatch.dev/categories/iac.md): breaking changes and end of support in IaC providers, modules, and languages. - [Other](https://eolwatch.dev/categories/other.md): lifecycle changes that do not fit another category. ## Data - [Item query](https://eolwatch.dev/data/items.json?status=upcoming): one page of the items that match the query parameters (cloud, type, category, service, q, from, to, within_days, status, sort, dir, limit, offset, detail). `type`, the kind of change, is retirement, end_of_support or breaking_change. `status` is upcoming, ended, in_effect or all. Without `status`: upcoming items only. 50 rows by default, 200 at most. With `detail=full`: 20 records by default, 50 at most. In a row, `days` is zero or negative once the period has started: read `state`. - [JSON export](https://eolwatch.dev/data/items.json): every published item in one file, for a script, with a field schema and a license note. In a conversation, use the item query. The license for the data has not been chosen yet, so no reuse terms are stated. - [CSV export](https://eolwatch.dev/data/items.csv): the same items and columns as the JSON export, in one file, for a script. - [Services](https://eolwatch.dev/data/services.json): every service that has a published item, with its counts, the date of its next item and the address of its Markdown form. - [Providers](https://eolwatch.dev/data/providers.json): every infrastructure as code provider, tool and module whose releases are read for breaking changes, with its newest tracked release and the address of its Markdown form. That form lists breaking changes release by release; add `?from=` to its address for the releases newer than that version. - [Changes](https://eolwatch.dev/data/changes.json): the changelog, newest first: items added, dates changed, items updated and items withdrawn. - [OpenAPI description](https://eolwatch.dev/openapi.json): every JSON data address listed here and every Markdown and JSON form, with its parameters and its answers. ## Schemas - [JSON Schema: item](https://eolwatch.dev/data/item.schema.json): one item record: the JSON form of an item page. - [JSON Schema: items](https://eolwatch.dev/data/items.schema.json): both answers of the items address: one page of a list, and the whole export. - [JSON Schema: services](https://eolwatch.dev/data/services.schema.json): the answer of the services address. - [JSON Schema: providers](https://eolwatch.dev/data/providers.schema.json): the answer of the providers address. - [JSON Schema: provider](https://eolwatch.dev/data/provider.schema.json): the JSON form of a provider page. - [JSON Schema: changes](https://eolwatch.dev/data/changes.schema.json): the answer of the changes address. - [JSON Schema: error](https://eolwatch.dev/data/error.schema.json): every error answer. ## Feeds - [RSS feed](https://eolwatch.dev/feed.xml): the most recently added items that are upcoming or were added in the last 30 days, at most 100. The JSON and CSV exports carry every published item. One cloud alone: `/feeds/.xml`, where cloud is azure, aws, gcp or oci. - [Atom feed](https://eolwatch.dev/atom.xml): the same items as the RSS feed. - [Calendar](https://eolwatch.dev/calendar.ics): one all-day event per dated upcoming item, in one file, for a calendar application. One cloud alone: `/feeds/.ics`, where cloud is azure, aws, gcp or oci. ## Optional - [Full list](https://eolwatch.dev/llms-full.txt): every upcoming item in one text, with its effective date, cloud, service and type, its source and the address of its Markdown form. Its first lines say whether the summary of each item is in it. For a question about a few items, use the item query. - [Agent access](https://eolwatch.dev/agents): this guidance as a page for people. HTML only. - [About](https://eolwatch.dev/about): what is tracked and how items are sourced and checked. HTML only.