Komodo Health Rate Limits

Komodo Health publishes no rate limits, quotas, throttling policy or rate-limit response headers for any of its surfaces. No document in the Marmot Development Kit documentation names a request ceiling, a concurrency cap, a burst allowance, an X-RateLimit-*/RateLimit-* header, a Retry-After behaviour, or a 429 response. Recorded as an honest zero rather than omitted. This is structural rather than an oversight. Komodo's primary developer surface is not a request-metered HTTP API: the SDK opens an authenticated DB-API connection to a per-account, Komodo-managed Snowflake warehouse, so throughput and cost are governed by that warehouse's sizing and the account's data subscriptions, not by an API quota. The App Builder and Marmot Analysis control planes behind api.komodohealth.com are authentication-gated with no public reference, so any limits they enforce are unobservable anonymously.