Cabolabs Rate Limits

CaboLabs publishes NO rate limits for either API. There is no quota, no burst allowance, no per-key or per-account ceiling, no 429 behaviour, and no X-RateLimit-* / RateLimit-* / Retry-After response header documented anywhere on atomik.app or cabolabs.com. The EHRServer error-code registry - the only complete status-code mapping either product publishes - contains no 429 row at all, across all 58 documented conditions, which corroborates that throttling is not part of the contract. An honest zero, and a structural one: both products are deployed per customer (Atomik as a licensed instance, EHRServer self-hosted), so capacity is whatever the operator provisions rather than a shared quota the vendor meters. The consequence for an agent is that there is no runtime signal to back off on - it cannot distinguish "slow down" from "broken" and must implement its own client-side ceiling.