openclaw - 💡(How to fix) Fix Feature: Support multiple API keys per provider as rate limit backup [1 comments, 2 participants]

• Manual key rotation (error-prone)

Fix Plan

To implement the proposed solution, follow these steps:

• Update the credential file format to support arrays of API keys:

  {
    "openai": ["key1", "key2", "key3"]
  }

• Modify the API client to rotate through the keys when a rate limit is detected (e.g., 429 response):

  import requests
  
  class APIClient:
    def __init__(self, keys):
      self.keys = keys
      self.current_key_index = 0
  
    def make_request(self, url, data):
      headers = {"Authorization": f"Bearer {self.keys[self.current_key_index]}"}
      response = requests.post(url, headers=headers, json=data)
      if response.status_code == 429:
        self.rotate_key()
        return self.make_request(url, data)
      return response
  
    def rotate_key(self):
      self.current_key_index = (self.current_key_index + 1) % len(self.keys)

• Implement a round-robin or sequential fail-over key rotation strategy:

  class APIClient:
    # ...
  
    def rotate_key(self):
      # Round-robin rotation
      self.current_key_index = (self.current_key_index + 1) % len(self.keys)
      # Sequential fail-over rotation
      # self.current_key_index += 1
      # if self.current_key_index >= len(self.keys):
      #   self.current_key_index = 0

Verification

To verify that the fix worked:

• Test the API client with multiple API keys and simulate rate limit responses (e.g., 429 status code)
• Verify that the client rotates through the keys correctly and makes successful requests after rotation

Extra Tips

• Consider implementing a backoff strategy to avoid overwhelming the API with requests after a rate limit is detected
• Monitor API key usage and adjust the rotation strategy as needed to ensure optimal performance and reliability.