I can help you resolve this. The error happens when request rates exceed the current plan’s limits. For high-volume client usage, upgrading to an Enterprise plan is usually the best approach, as it offers higher rate limits and dedicated support. Additionally, implementing rate-limiting strategies (like request batching, retries with exponential backoff, or queuing) can prevent cooldown errors even on pay-as-you-go plans, though there are still inherent limits. I can assist in both optimizing your SDK usage and planning the upgrade to handle multiple clients efficiently. @MarioBarrientos