Tl Dv Rate Limits

tl;dv publishes NO rate limits. The API reference at doc.tldv.io has no rate limit section, no quota table and no documented response headers, and no limits appear on the pricing page. This is an honest zero, not an unchecked field — and it is a real gap rather than an absence of throttling, because two independent signals show the API does throttle: (1) tl;dv's OWN official MCP server retries on HTTP 429. src/api/tldv-api.ts treats `status === 429` as a retryable condition alongside 5xx and network errors, backing off exponentially (1s, 2s, 4s …) up to a capped delay. A provider does not write 429 handling into its first-party client unless the service returns 429. (2) The API is fronted by Cloudflare (server: cloudflare, cf-ray on every response), which applies edge rate limiting independently of anything tl;dv documents. An agent therefore has no published budget to plan against and no runtime signal to react to: it can only discover the limit by hitting it.