specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: AO Smith
providerId: ao-smith
generated: '2026-09-02'
method: searched
source: https://www.hotwater.com/resources/mobile-apps.html
created: '2026-05-04'
modified: '2026-09-02'
tags:
  - IoT
  - Manufacturing
  - Smart Home
  - Water Heaters
  - Rate Limiting
limit_count: 0
limits: []
headers: {}
responseCodes: {}
description: >-
  A. O. Smith documents no API rate limits. There is no developer reference, no published
  throttling policy, and no documented response headers, because there is no published API
  — the only live surface is an undocumented Apollo GraphQL endpoint serving the iCOMM
  mobile app. An honest zero: nothing about A. O. Smith's runtime limit behaviour is
  knowable from what they publish.
note: >-
  REPLACES A FABRICATED SCAFFOLD. Until 2026-09-02 this file asserted five rate limits
  (10/100/1000 requests per minute across free/professional/enterprise tiers), an
  X-RateLimit-* header family and a RateLimit-Policy header, none of which A. O. Smith has
  ever published. It was written by the 2026-05-04 bulk sweep (roadmap#35). Per STEP 24,
  undocumented limits are recorded as limit_count 0 rather than as placeholder numbers —
  this deliberately drops the agent-readiness `rate_limit_signal` credit the invented
  artifact was earning.
searched:
  - url: https://www.hotwater.com/resources/mobile-apps.html
    status: 200
    finding: Consumer app documentation only; no limits, no headers.
  - url: https://r2.wh8.co/graphql
    status: 200
    finding: >-
      Live Apollo Server; introspection disabled and unauthenticated calls are rejected, so
      no limit headers were observable on an anonymous response.
maintainers:
  - FN: Kin Lane
    email: info@apievangelist.com
    X: apievangelist
    url: https://apievangelist.com