Muck Rack Rate Limits

An honest zero. Muck Rack publishes NO numeric rate limit anywhere public, yet its API Terms Addendum makes exceeding rate limits a breach — it prohibits use "in a manner that exceeds rate limits, or constitutes excessive or abusive usage". The obligation is therefore contractually binding and numerically unknowable to a consumer, which is the finding. No RateLimit-*, X-RateLimit-* or Retry-After header appeared on any observed response, so there is no runtime signal an agent could back off against either; the only rate-shaping headers present are Cloudflare edge headers. Pricing is described as depending on "how much data you need and how frequently you request it", which implies a negotiated per-contract quota rather than a published tier limit. limit_count is 0 because nothing quantified is published — not because no limit is enforced.