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: Equipmentwatch
providerId: equipmentwatch
generated: '2026-09-06'
method: probed
created: '2026-05-04'
modified: '2026-09-06'
source: >-
  The published OpenAPI at https://docs.equipmentwatchapi.com/openapi.yaml, the API pages
  under https://equipmentwatch.com/api/, and live unauthenticated responses from
  https://equipmentwatchapi.com/v1/taxonomy/categories and
  https://sandbox.equipmentwatchapi.com/v1/taxonomy/categories, all on 2026-09-06.
tags:
  - Construction
  - Equipment
  - Rate Limiting
  - Quotas
  - Throttling

limit_count: 0
limits: []

description: >-
  EquipmentWatch documents no rate limits and emits no rate-limit headers. An integrator has
  no published ceiling to design against and no runtime signal to back off from. This is an
  honest zero, measured — not an unexamined gap.

response_headers:
  observed: []
  checked_for:
    - X-RateLimit-Limit
    - X-RateLimit-Remaining
    - X-RateLimit-Reset
    - RateLimit-Limit
    - RateLimit-Remaining
    - RateLimit-Reset
    - RateLimit-Policy
    - Retry-After
  evidence:
    - url: https://equipmentwatchapi.com/v1/taxonomy/categories
      status: 401
      rate_limit_headers_present: false
    - url: https://sandbox.equipmentwatchapi.com/v1/taxonomy/categories
      status: 401
      rate_limit_headers_present: false
  caveat: >-
    Both observations are on unauthenticated 401 responses — the only responses obtainable
    without an issued key. It remains possible that authenticated responses carry limit
    headers. That cannot be confirmed and is NOT assumed here.

status_on_exhaustion: undocumented

documented_limits:
  found: false
  searched:
    - https://docs.equipmentwatchapi.com/openapi.yaml
    - https://equipmentwatch.com/api/
    - https://equipmentwatch.com/api/taxonomy/
    - https://equipmentwatch.com/api/values/
    - https://equipmentwatch.com/api/costs/
    - https://equipmentwatch.com/api/rental/
    - https://equipmentwatch.com/api/specs/
    - https://equipmentwatch.com/api/verification/
    - https://equipmentwatch.com/api/market-data/
  note: >-
    Zero matches for rate limit, throttle, quota, requests per, 429 or Retry-After across the
    spec and the developer surface.

adjacent_ceilings:
  note: >-
    These are NOT rate limits. They are recorded because they are the only published numeric
    ceilings on the API and are easily confused with throttling.
  ceilings:
    - name: pagination page size
      value: 50
      unit: items per response
      source: components/parameters/limitParam in the published OpenAPI (minimum 1, maximum 50, default 50)
      implication: >-
        A full pull of the model corpus through /taxonomy/models requires paging 50 rows at a
        time with no total count in the response. The /bulk/models and /bulk/manufacturers
        operations exist precisely to avoid this, and are the right choice for a mirror.

superseded_content:
  note: >-
    This file previously carried five invented per-tier limits (10/100/1000 rpm, 1,000 and
    100,000 requests/month, burst ceilings) plus four policy paragraphs describing backoff,
    burst handling, quota reset and fair use. None of it was published by EquipmentWatch;
    it was written by the 2026-05-04 API Evangelist bulk sweep as a scaffold and its own
    description said so. It has been removed. An invented Retry-After policy is worse than
    no policy — it tells an agent to trust a signal that will never arrive.
  removed: '2026-09-06'
  removed_by: enrichment pipeline local-v3

maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com