Rate limit improvements

We have made a handful of improvements to our rate limits to help maintain a high-quality API and support optimal performance. Some of these updates include:

1. Standardized error codes: Rate limit errors will now return a 429 HTTP error code to help standardize responses and simplify error handling.
2. Retry-After header: Errors will now include the Retry-After header to indicate how long you need to wait before making another request.
3. New rate limits: We've introduced new limits, including per-minute request limits and a concurrency limit. These changes help reduce the frequency of complexity limits, giving you more control over your API usage and providing a smoother developer experience.
4. Daily limits: Daily request limits will be enforced for basic and standard accounts starting next week. Limits for pro and enterprise accounts will be gradually rolled out next year.

For more information, check out our rate limits documentation. Questions or comments? Add them here!