Lvt Rate Limits

LVT publishes NO numeric rate limits for the Partner API. All 33 operations in the OpenAPI were checked: not one declares a 429 response, and components.responses contains no 429 at all. No X-RateLimit-*, RateLimit-* or Retry-After header is documented anywhere. The only statement on the subject is prose in the webhooks topic of the Partner API manual: "Use of LVT's Partner API is metered, and LVT can block clients who spam or flood the service. The result for when you call /publicKeys should be cached and reused." That tells an integrator a limit exists and that exceeding it can get them blocked, but gives no window, no quota, and no runtime signal — an agent cannot tell how close it is, and cannot learn from the response that it has been throttled. Recorded as an honest zero.