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: Cohesity providerId: cohesity generated: '2026-09-05' method: searched source: >- https://developers.cohesity.com/docs/getting-started, https://developer.cohesity.com/apidocs/versions/, openapi/*.yml, https://learn.microsoft.com/en-us/connectors/cohesitygaiamcp/ created: '2026-05-04' modified: '2026-09-05' limit_count: 1 headers_published: false description: >- Cohesity publishes essentially no API rate limits. This file replaces a 2026-05-04 bulk-sweep scaffold that invented free/professional/enterprise tiers at 10/100/1000 requests per minute plus monthly quotas and a full X-RateLimit-* header set; none of that is published by Cohesity and it has all been removed. The four published specifications were searched for rate-limit response headers, 429 responses and throttling parameters: there are none. The only quantitative limit Cohesity publishes anywhere applies to the Microsoft Power Platform connector, not to the REST API itself. headers: {} headers_note: >- No X-RateLimit-*, RateLimit-* or Retry-After header is declared in any published Cohesity specification or documented on any Cohesity docs page. An agent gets no runtime budget signal from this API. responseCodes: throttled: null note: >- No operation in any of the four published specs declares a 429 response. All 687 operations declare only a `default` error response. limits: - name: Cohesity Gaia MCP / Gaia connector - Power Platform connection limit scope: per-connection limit: 100 window: 60s metric: calls applies: [Cohesity Gaia MCP, Cohesity Gaia] source: https://learn.microsoft.com/en-us/connectors/cohesitygaiamcp/ note: >- This is the Microsoft Power Platform connector throttle, published by Microsoft for the connector wrapper. It is the only numeric API rate limit associated with Cohesity anywhere in public. It does NOT describe the Cohesity REST API or the raw MCP server. platform_throttling: note: >- Cohesity does publish resource throttling that is often mistaken for API rate limiting but is not: `rateLimitBytesPerSec` on replication/archival transfers and the MapReduce background-activity throttling schedule (/public/cluster/backgroundActivitySchedule). These govern data movement bandwidth, not request rates, and are recorded here only so they are not miscounted as API limits. policies: [] evidence: - {url: 'https://developers.cohesity.com/docs/getting-started', status: 200, finding: no rate limits documented} - {url: 'https://developer.cohesity.com/apidocs/versions/', status: 200, finding: no rate limits documented} - {url: 'https://learn.microsoft.com/en-us/connectors/cohesitygaiamcp/', status: 200, finding: '100 calls / 60 seconds per connection'} maintainers: - FN: Kin Lane email: kin@apievangelist.com