openclaw - 💡(How to fix) Fix Feature Request: Support multiple Tavily API keys for failover [1 participants]

Problem

When the Tavily API key reaches its rate limit or runs out of quota, users need to manually switch to another API key. Currently, OpenClaw only supports a single Tavily API key configuration, which is inconvenient for users who have multiple keys.

Use Case

In a production environment, users may have:

• Multiple Tavily accounts with separate API keys
• Different rate limits per key
• Need for seamless failover when one key is exhausted

Expected Behavior

Support configuring multiple Tavily API keys, with automatic failover when the primary key is rate-limited or exhausted.

Suggested Implementation

1. Allow apiKey in plugins.entries."tavily-search".config to be an array:

   plugins:
     entries:
       "tavily-search":
         enabled: true
         config:
           apiKey:
             - key_1
             - key_2
             - key_3

2. OpenClaw automatically rotates to the next key when:

   • Rate limit (429) is hit
   • Quota exhaustion error is returned

3. Alternatively, support environment variable fallback:

   TAVILY_API_KEY_1=xxx
   TAVILY_API_KEY_2=xxx

Benefits

• Improved reliability for production deployments
• Better cost management (switching keys when one runs out)
• Seamless user experience without manual intervention

Related

• Current config: plugins.entries."tavily-search".config.apiKey (single string)
• Tavily API documentation: https://tavily.com