Rate limits won't come into play unless you're bot is attempting to submit multiple orders consecutively due to finding spreads very close to each other. All real-time data being used by the bot is done via public websocket connections, so the bot isn't making any REST calls until it's time to submit orders. Since most rate limits are for within a certain time period, i.e. X calls within 60 seconds, your bot would have to find a lot of spreads within 60 seconds to trigger a rate limit. This is still in beta though, part of the beta will involve testing these things and collecting data on how bots are working for our users. We'll see!