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: Motadata
providerId: motadata
created: '2026-05-04'
generated: '2026-08-29'
modified: '2026-08-29'
method: searched
source: >-
  https://docs.motadata.com/serviceops-docs/setup-and-operations/on-premises-installation/installation-guides/advanced-configurations/how-to-configure-api-rate-limit
tags:
  - AIOps
  - Monitoring
  - Rate Limiting
description: >-
  Motadata ServiceOps ships a configurable token-bucket API rate limiter. Because ServiceOps is
  self-hosted, these are DEFAULTS the customer's administrator can change in advanced
  configuration, not limits Motadata enforces on a shared multi-tenant service — there is no
  per-plan or per-key quota, and no metered tier. Limits can also be scoped to named API groups
  by path and HTTP method. ObserveOps documents no API rate limit.
  This file replaced a 2026-05-04 bulk-sweep scaffold whose free/professional/enterprise tiers
  and per-month quotas were invented; none of them exist.
algorithm: token-bucket
scope: server-wide, with optional per-API-group overrides
configurable: true
headers:
  limit: X-RateLimit-Limit
  remaining: X-RateLimit-Remaining
  reset: X-RateLimit-Reset
reset_units: milliseconds
responseCodes:
  throttled: null
  note: >-
    Motadata's rate-limit page documents the three response headers but does NOT state the HTTP
    status or error body returned when the bucket is empty. Recorded as unknown rather than
    assumed to be 429.
limits:
  - tier: default
    name: ServiceOps default API rate limit
    scope: server
    metric: requests_per_second
    limit: 20
    burst: 30
    timeFrame: second
    configurable: true
    settings:
      enabled: true
      apply-default-rate-limiting: true
      refill-rate: 20
      refill-interval: 1
      bucket-capacity: 30
      initial-bucket-capacity: 30
      token-cache-timeout-minutes: 30
    applies:
      - Motadata ServiceOps
    source: >-
      https://docs.motadata.com/serviceops-docs/setup-and-operations/on-premises-installation/installation-guides/advanced-configurations/how-to-configure-api-rate-limit
groups:
  supported: true
  keys:
    - name
    - routes
    - path
    - methods
  description: >-
    Named API groups can carry their own bucket settings, selected by request path and HTTP
    method, so an administrator can rate-limit one route family differently from the rest.
limit_count: 1
observeops:
  documented: false
  note: >-
    No published API rate limit for ObserveOps was found in its API documentation or in the
    official observeops CLI, which implements retry/backoff for transport failures but carries
    no rate-limit header handling.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com