Facets Rate Limits

REPLACES A SCAFFOLD, AND THE HONEST ANSWER IS ZERO. Until 2026-09-07 this file asserted invented limits (10 req/min free, 100 req/min professional, 429 on exhaustion, a full set of X-RateLimit-* headers) written by the 2026-05-04 bulk sweep. None of it is published by Facets. What we actually found: - The OpenAPI document contains zero occurrences of "RateLimit", "X-RateLimit" or "Retry-After", and declares no 429 response on any of its 629 operations. The only statuses any operation declares are 200, 400, 403, 404, 405, 409 and 500. - No page in the 282-URL docs sitemap documents an API rate limit, quota or throttle. - Pricing (https://www.facets.cloud/pricing) meters Resource Instances, not API calls; there is no request quota in any tier. This is plausible rather than surprising for the deployment model: each customer gets their own control plane (SaaS) or self-hosts it entirely (Enterprise), so there is no shared multi-tenant API surface to protect with a published global limit. That explains the absence; it does not remove the consequence, which is that an automation client has NO published signal telling it when to back off, and no documented status code to key retry logic on.