specification: API Commons Rate Limits
specificationVersion: '0.1'
provider: Moogsoft
providerId: moogsoft
generated: '2026-08-29'
method: searched
source: https://api.docs.moogsoft.com/docs/latest/branches/main/eb1492ed9496e-api-license-and-disclaimer
  and https://api.docs.moogsoft.com/docs/latest/branches/main/1sy0hr6odnj10-incident-management-api-documentation
created: '2026-05-04'
modified: '2026-08-29'
limit_count: 0
description: Moogsoft publishes NO numeric rate limits for the APEX AIOps Incident Management APIs. This
  file replaces a 2026-05-04 API Evangelist scaffold that asserted invented per-tier quotas (10/min free,
  100/min professional, 1000/min enterprise) which the provider has never published. What Moogsoft does
  publish is a response-size cap and a reservation of the right to throttle.
headers:
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
  note: No X-RateLimit-*, RateLimit-* or Retry-After header is declared in any of the 17 OpenAPI contracts,
    and none was returned on a live unauthenticated request to https://api.moogsoft.ai/ (HTTP 401).
responseCodes:
  throttled: null
  note: 429 does not appear in any published response set. Declared error codes are 400, 401, 404, 408,
    500 plus 4XX/5XX wildcards.
limits: []
published_constraints:
- kind: response-size-cap
  scope: per-request
  applies_to: all GET operations
  limit: 1000
  unit: records
  quote: Incident Management Engineering has adopted a policy of limiting GET requests to a maximum of
    1000 records. You can retrieve all records, but you should use multiple iterative requests to retrieve
    large data sets.
  source: https://api.docs.moogsoft.com/docs/latest/branches/main/1sy0hr6odnj10-incident-management-api-documentation
- kind: discretionary-throttle
  scope: platform
  limit: null
  quote: Incident Management might apply sensible concurrency and rate limits when the integrity of the
    Incident Management platform and/or service degradation is at risk, even if an individual resource
    has no rate limits currently.
  source: https://api.docs.moogsoft.com/docs/latest/branches/main/eb1492ed9496e-api-license-and-disclaimer
  note: Explicitly discretionary and unquantified. A client cannot plan against it or detect it from a
    header.
gaps:
- No published numeric limit for any endpoint or tier.
- No rate-limit response headers, so an agent has no runtime signal of remaining budget.
- No documented 429 behaviour or Retry-After semantics.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com