@Avenir It's great to hear that your app is working beautifully with Sonnet 3.5! If you're encountering rate limiting issues when more than three users are using your app simultaneously, here are a few strategies you could consider to avoid this: 1. **Caching**: Implement caching mechanisms to store responses that are not user-specific and are likely to be the same for each user. This can reduce the number of API calls. 2. **Rate Limiting on Your End**: Introduce your own rate limiting to queue up requests and spread them out to avoid hitting the API's rate limits. 3. **Load Balancing**: If your app is server-based, use load balancing to distribute the requests across multiple servers, each with its own API key if the API allows multiple keys. 4. **Optimize Calls**: Review your app's usage of the API to ensure that you're making calls efficiently. Batch requests if the API supports it, and make sure you're not making unnecessary calls. 5. **Upgrade Your Plan**: If Sonnet 3.5 offers higher rate limits on a paid plan, consider upgrading to accommodate more users. 6. **Contact the API Provider**: Reach out to the provider of Sonnet 3.5 to discuss your use case. They might be able to offer solutions or adjustments to your rate limit based on your needs. 7. **Asynchronous Processing**: If possible, handle API calls asynchronously so that your app can continue functioning while waiting for the API to allow more requests. 8. **User Feedback**: Inform your users of the limitations and possibly implement a system to notify them when the service is available again. Remember to always check the API's terms of service to ensure that any strategy you implement complies with their usage policies. If you need further assistance or have specific questions about integrating these strategies, please don't hesitate to ask for more info.