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: Zype providerId: zype generated: '2026-08-28' method: searched source: https://docs.zype.com/reference/welcome-to-the-zype-api-documentation, https://www.zype.com/pricing, and header/response analysis of the 15 files in openapi/ created: '2026-05-04' modified: '2026-08-28' tags: - Rate Limiting - Quotas - Throttling description: Zype publishes no API rate limits. This file records that absence with the evidence for it, replacing a 2026-05-04 generated scaffold that asserted 10/100/1000 req-per-minute tiers and X-RateLimit-* headers Zype has never documented. note: 'HONEST ZERO. Searched: the docs overview page (which documents authentication, errors, pagination and video formats but says nothing about limits), every reference page listed in docs.zype.com/llms.txt, the pricing page, and all 15 OpenAPI files. No X-RateLimit-*, RateLimit-*, or Retry-After header is declared on any of the 317 operations; the token 429 appears exactly once across ~1.1MB of specification. There is a real hard limit on page size — per_page maximum 100 on every list operation — and that is the only published quantitative bound on API consumption, so it is recorded below as a pagination limit rather than a rate limit.' limit_count: 0 limits: [] headers: limit: null remaining: null reset: null retryAfter: null policy: null response_codes: throttled: null note: 429 is declared on exactly one operation across all 15 specs and is documented nowhere. related_published_bounds: - name: per_page maximum value: 100 scope: every list operation source: https://docs.zype.com/reference/welcome-to-the-zype-api-documentation note: Pagination is mandatory on all list requests; default 10, maximum 100. An agent enumerating a large library is bound by this, not by a rate limit. commercial_model: API access is bundled into the product tier (see plans/zype-plans-pricing.yml). Encoding and content delivery are metered at "preferred usage rates" that are not published, but API requests themselves are not a metered unit. maintainers: - FN: Kin Lane email: kin@apievangelist.com