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: Ant Media
providerId: ant-media
created: '2026-05-04'
modified: '2026-09-02'
generated: '2026-09-02'
method: searched
source: >-
  https://docs.antmedia.io/guides/developer-sdk-and-api/rest-api-guide/ and
  https://antmedia.io/pricing/ (both HTTP 200, 2026-09-02), plus the six published OpenAPI
  documents in openapi/.
supersedes: >-
  The 2026-05-04 bulk-sweep scaffold, which invented free/professional/enterprise tiers with
  10/100/1000 requests per minute and monthly quotas. None of those exist. They are removed
  here rather than left to be read as Ant Media's published limits.
limit_count: 0
description: >-
  Ant Media Server publishes NO API rate limits. This is not an omission in the documentation —
  it follows from the delivery model. The server is software the customer runs on their own
  hardware, so there is no vendor-side meter to enforce, and Ant Media states on its pricing
  page that licensing imposes no connection or concurrent-viewer limit either. Throughput is
  bounded by the operator's CPU, memory, network and cluster size.
headers:
  published: false
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
  detail: >-
    No X-RateLimit-*, no RateLimit-*, and no Retry-After appears in any of the six OpenAPI
    documents or in the REST API guide. An agent gets no runtime backpressure signal from this
    API at all.
responseCodes:
  throttled: null
  detail: >-
    429 is not declared on any operation and is not mentioned in the docs. The declared error
    codes are 400 (4 operations), 404 (3 operations) and an untyped `default` (19 operations);
    everything else declares only 200. See errors/ant-media-problem-types.yml.
limits: []
capacity_controls:
  note: >-
    Ant Media has no request-rate controls, but it does ship per-resource capacity controls
    that an operator sets themselves. These are viewer ceilings, not API throttles, and they
    are recorded here so the honest zero above is not mistaken for "no controls of any kind".
  controls:
    - field: webRTCViewerLimit
      scope: broadcast
      source: Broadcast schema, openapi/ant-media-broadcasts-api-openapi.yml
    - field: hlsViewerLimit
      scope: broadcast
      source: Broadcast schema, openapi/ant-media-broadcasts-api-openapi.yml
    - field: dashViewerLimit
      scope: broadcast
      source: Broadcast schema, openapi/ant-media-broadcasts-api-openapi.yml
    - field: subtracksLimit
      scope: broadcast (conference main track)
      source: Broadcast schema, openapi/ant-media-broadcasts-api-openapi.yml
    - field: IP Filter Settings
      scope: application
      note: An allow-list of IPs/CIDRs, the default protection on the REST API. Access control, not rate control.
      source: https://docs.antmedia.io/guides/developer-sdk-and-api/rest-api-guide/securing-rest-apis/
  webhook_retry:
    webhookRetryCount: 0
    webhookRetryDelay: 1000
    note: Outbound webhook retry policy, operator-configurable. Default retry count is 0.
    source: https://docs.antmedia.io/guides/advanced-usage/webhooks/
published_statement:
  quote: >-
    "Ant Media Server licensing does not impose fixed limits on connections or concurrent
    viewers. Actual capacity depends on your infrastructure resources, server configuration,
    and scaling architecture."
  source: https://antmedia.io/pricing/
maintainers:
  - FN: Kin Lane
    email: info@apievangelist.com
    url: https://apievangelist.com