feat: add rate limiting support for model providers #318
+1,702
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds rate limiting capabilities to Strands model providers using a token bucket algorithm to ensure compliance with API providers' RPM limits.
Motivation:
ReAct agents create unpredictable API call patterns—a simple task might need 2 calls while complex reasoning could chain 20+ calls. Here are a few scenarios where rate limiting helps:
Basic Usage:
Key Features:
Implementation Details:
I'd appreciate any feedback if you have concerns about the feature or suggestions for improvement!
Related Issues
N/A
Documentation PR
Will add docs if feature is approved
Type of Change
New feature
Testing
How have you tested the change? Verify that the changes do not break functionality or introduce warnings in consuming repositories: agents-docs, agents-tools, agents-cli
hatch run prepare
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.