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: EMC
providerId: emc
generated: '2026-08-29'
method: searched
modified: '2026-08-29'
source: >-
  Searched the reachable EMC/Dell developer surface and read EMC's own first-party clients
  (github.com/EMCECS/python-ecsclient, github.com/dell/PyU4V) on 2026-08-29 for
  rate-limit handling. Neither client sets, reads, or retries on any rate-limit header.
tags:
  - Cloud Infrastructure
  - Enterprise Storage
  - Object Storage
  - Rate Limiting
description: >-
  Rate limits for the EMC management APIs. There are none published, and this file records
  that as a measurement rather than omitting itself. NOTE: this artifact previously
  contained scaffold values — invented free/professional tiers with 10 and 100
  requests-per-minute quotas — written by the 2026-05-04 bulk sweep. Those were never
  EMC's numbers and have been removed.
limit_count: 0
limits: []
headers:
  published: false
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
responseCodes:
  throttled: null
  quotaExceeded: null
finding: >-
  The EMC ECS Management REST API and the Unisphere REST API are appliance APIs served by
  hardware the customer owns and operates. There is no EMC-operated gateway between the
  caller and the array, no per-key quota, and no metered plan — so there is nothing for
  EMC to rate-limit and nothing to publish. Throughput is bounded by the customer's own
  cluster. EMC's own client libraries carry no RateLimit-*, X-RateLimit-* or Retry-After
  handling of any kind, and no 429 appears anywhere in the 176-code ECS error registry
  (see errors/emc-error-codes.yml), which is strong corroboration that the API does not
  emit one.
agent_impact: >-
  An agent gets no runtime backpressure signal from these APIs. The only availability
  signal published is ECS error code 6000, "Unable to connect to the service. The service
  is unavailable, try again later", together with the per-response `retryable` boolean in
  the error envelope. Those are the retry primitives; there is no reset time to wait for.