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: CloudChipr
providerId: cloudchipr
generated: '2026-09-05'
method: searched
source: >-
  https://docs.cloudchipr.com/ (full llms.txt page index, 60 pages) +
  openapi/cloudchipr-enterprise-api-openapi.yml + live unauthenticated probes of
  https://api.cloudchipr.com and https://mcp.cloudchipr.com/mcp
created: '2026-05-04'
modified: '2026-09-05'
limit_count: 0
supersedes: >-
  REPLACES the 2026-05-04 bulk-sweep scaffold, which invented five numeric limits (10/100/1000 rpm,
  1k/100k monthly quotas) and a full X-RateLimit-* header set. CloudChipr publishes none of that.
  An honest zero is the finding.
description: >-
  CloudChipr publishes NO rate limits for the Enterprise API or the MCP server, and the contract
  declares no throttling response. This is a genuine documented-absence, verified three ways.

headers:
  documented: []
  observed: []
  note: >-
    No RateLimit-*, X-RateLimit-* or Retry-After header is documented in the docs or declared in
    the spec. Unauthenticated requests to api.cloudchipr.com return 401 with a zero-length body and
    no rate-limit headers, so nothing could be observed live either. The MCP endpoint returns 401
    with only a `www-authenticate: Bearer` challenge and `strict-transport-security`.

responseCodes:
  throttled: null
  note: >-
    No 429 response is declared on ANY of the 26 operations. The declared failure codes are 400,
    401, 404, 405 and 500 only. An agent has no contractual signal that it has been throttled and
    no documented backoff instruction.

limits: []

evidence:
  - check: docs sweep
    detail: >-
      The published documentation index (https://docs.cloudchipr.com/llms.txt, 60 pages) contains no
      rate-limit, quota or throttling page. The API Keys page documents key count (2) and expiry
      (1-365 days) but no request limits.
    checked: '2026-09-05'
  - check: spec sweep
    detail: 'Zero 429 responses and zero RateLimit/Retry-After headers across 26 operations in the 123KB OpenAPI.'
    checked: '2026-09-05'
  - url: https://api.cloudchipr.com/
    status: 401
    detail: Empty body, no rate-limit headers.
    checked: '2026-09-05'
  - url: https://mcp.cloudchipr.com/mcp
    status: 401
    detail: 'Bearer challenge only; no rate-limit headers.'
    checked: '2026-09-05'

adjacent_limits_note: >-
  These are real published caps, but they are ACCOUNT limits, not request limits. Recorded here so
  a reader does not mistake their absence above for no limits at all.
adjacent_limits:
  - name: API keys per account
    limit: 2
    source: https://docs.cloudchipr.com/docs/api-keys
  - name: API key lifetime
    limit: '1 to 365 days'
    source: https://docs.cloudchipr.com/docs/api-keys
    superseded_note: 'The 2026-07-01 release notes state the expiration requirement was removed.'
  - name: Connected cloud accounts
    limit: '2 (Basic) / 10 (Advanced) / 20 (Pro) / 20+ (Enterprise)'
    source: https://cloudchipr.com/pricing
  - name: Integrations
    limit: '3 (Advanced) / unlimited (Pro, Enterprise)'
    source: https://cloudchipr.com/pricing
  - name: Cloud resource collection interval
    limit: every 15 minutes
    source: 'https://cloudchipr.com/pricing - "Check Every 15m"'

agent_risk: >-
  With no published limit, no 429 in the contract and no Retry-After, an agent driving the
  unbounded collection operations (POST /accounts/{accountId}/resources returns every live resource
  in an account with no pagination) has neither a size bound nor a throttling signal to back off
  against.

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