# A. O. Smith Corporation

> A. O. Smith (NYSE: AOS) is a global manufacturer of residential and commercial water
> heaters, boilers, water treatment and air purification products, headquartered in
> Milwaukee, Wisconsin. Its connected-product line runs on the iCOMM platform, which
> lets homeowners and plumbing professionals monitor and control compatible water
> heaters from a mobile app.
>
> A. O. Smith does NOT operate a public developer program. There is no developer portal,
> no API reference, no OpenAPI/AsyncAPI/GraphQL SDL, no SDK, and no MCP server. This file
> was GENERATED by API Evangelist from the catalog profile and live probes on 2026-09-02
> — it is not published by A. O. Smith.

## What exists

- [iCOMM connected water heaters](https://www.hotwater.com/resources/mobile-apps.html): the
  iCOMM Connectivity app for professionals and the A. O. Smith app for homeowners. Remote
  temperature control, vacation mode, leak and maintenance alerts, energy-use history.
- [Connected residential water heaters](https://www.hotwater.com/water-heaters/residential/connected/):
  the product line the platform serves.
- Third-party integrations exist for home-automation platforms (Home Assistant ships an
  `aosmith` integration; Hubitat has a community driver), all built on reverse-engineered
  access rather than a documented API.

## API surface — what a machine can actually reach

- There is no published contract. Probed 2026-09-02: `/openapi.json`, `/openapi.yaml`,
  `/swagger.json`, `/api-docs`, `/docs` and `?wsdl` return 404 on every A. O. Smith host,
  as do all ten `/.well-known/*` discovery paths including `agent-card.json` and
  `agent.json`.
- `https://api.aosmith.com`, long carried in this catalog as the base URL, DOES NOT EXIST
  — the name has no DNS record.
- The real iCOMM backend is an Apollo GraphQL endpoint at `https://r2.wh8.co/graphql`. It
  is A. O. Smith infrastructure: `r2.wh8.co` CNAMEs to
  `router-default.apps.aosmith-prod.hd1m.p1.openshiftapps.com`, the same OpenShift cluster
  that hosts their 3scale portal. It is undocumented, requires app credentials, and returns
  `GRAPHQL_VALIDATION_FAILED — introspection is not allowed` to any schema query. Agents
  cannot discover its shape.
- A. O. Smith runs a Red Hat 3scale developer portal at
  `https://3scale.apps.aosmith-prod.hd1m.p1.openshiftapps.com/`, but it is a stock
  unconfigured install: the only API it advertises is 3scale's built-in "Echo API" demo.
  API management is deployed; no API has been published through it.

## Unofficial clients (NOT first-party)

- [py-aosmith](https://pypi.org/project/py-aosmith/) — Python, v1.0.18 (2026-05-21). Backs
  the Home Assistant `aosmith` integration. Its README states it "is not an official API"
  and is "not affiliated with or endorsed by A. O. Smith."
- [node-aosmith](https://www.npmjs.com/package/node-aosmith) — JavaScript, v1.0.1
  (2023-11-27), stale.

## Company

- [Corporate site](https://www.aosmith.com/)
- [Hot water brand site](https://www.hotwater.com/)
- [News](https://www.aosmith.com/news.html)
- [Contact](https://www.aosmith.com/about-us/contact.html)
- [Terms and conditions](https://www.aosmith.com/terms-and-conditions.html)
- [Privacy policy](https://www.aosmith.com/privacy-policy)
- [Investor relations](https://investor.aosmith.com/)
- [LinkedIn](https://www.linkedin.com/company/a-o-smith-corporation)

## Notes for agents

- Nothing here is callable without A. O. Smith consumer-account credentials, and even then
  the contract is undocumented and unstable by the maintainers' own warning.
- If you need A. O. Smith device data, the realistic path today is the Home Assistant
  integration, not a vendor API.