generated: '2026-09-02' method: searched source: >- https://www.apiable.io/docs/api-reference/; openapi/apiable-platform-api-openapi.json; https://www.apiable.io/docs/products/plans/rate-limits/ provider: Apiable providerId: apiable api: Apiable Platform API v2 limit_count: 0 note: >- Apiable publishes NO rate limits for its own Platform API. The OpenAPI 3.1 document's info description contains a "## Rate Limiting" heading with no content beneath it, no operation declares a 429 response, and no RateLimit-*, X-RateLimit-* or Retry-After header appears anywhere in the 66 operations or in the documentation. An honest zero, probed 2026-09-02. This artifact REPLACES a generated scaffold written by the 2026-05-04 bulk sweep, which asserted free/professional/enterprise tiers with invented per-minute and per-month numbers and invented response headers. None of those values were published by Apiable and all have been removed. headers: limit: null remaining: null reset: null retryAfter: null policy: null note: no rate-limit response headers are documented responseCodes: throttled: null note: 429 is not declared on any operation in the published contract limits: [] product_feature_context: note: >- Apiable's product DOES manage rate limits — but for its customers' APIs, enforced by the customer's own gateway, not by Apiable. This is recorded as context only and is not a limit on the Apiable Platform API. docs: https://www.apiable.io/docs/products/plans/rate-limits/ model: - gateway: AWS API Gateway fields: [Quota Limit, Quota Period (Month/Week/Day), Throttle RateLimit, Throttle BurstLimit] - gateway: Kong fields: [Second, Minute, Hour, Day, Month, Year] - gateway: other fields: [] note: rate limit fields are not offered for gateway types other than AWS and Kong constraint: >- Rate limits are available on Gateway-bound plans only; the Limits tab is disabled on Catalog-bound plans, and all of a plan's APIs must live on one gateway. maintainers: - FN: Kin Lane email: info@apievangelist.com