Malt Rate Limits

Malt publishes NO numeric rate limits. The API documentation's own getting-started list tells a developer they will need to "understand the usage limits and best practices" under a heading called "Rate Limiting Guidelines" — but no such section exists anywhere in the published document. There is no requests-per-second, per-minute or per-day figure, no burst allowance, no per-key or per-account quota, and no documented 429 behaviour. Live unauthenticated requests to both halves of the surface return HTTP 401 with an empty body and carry NO rate-limit headers of any family — no X-RateLimit-*, no RFC 9239-style RateLimit-*, no Retry-After. Recorded as limit_count: 0: an honest zero, not an unchecked field. This is the clearest single gap on Malt's API surface — the docs promise a limits section and then do not ship one, so an agent or integration has no way to pace itself except by observing failures.