From 6cfd0632c745fb2a383f9e7c070cf192b3aeb582 Mon Sep 17 00:00:00 2001 From: Brian Sparker Date: Fri, 26 Jun 2026 12:26:19 -0400 Subject: [PATCH] docs: mention legacy YOUCOM_API_KEY in example config comment Addresses review feedback: the example comment now notes both YDC_API_KEY and the legacy YOUCOM_API_KEY so existing users aren't confused. Co-Authored-By: Claude Opus 4.8 (1M context) --- .../example_config_yaml/websearch_interception_config.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/litellm/proxy/example_config_yaml/websearch_interception_config.yaml b/litellm/proxy/example_config_yaml/websearch_interception_config.yaml index bf6be24299e..bb7c50ce272 100644 --- a/litellm/proxy/example_config_yaml/websearch_interception_config.yaml +++ b/litellm/proxy/example_config_yaml/websearch_interception_config.yaml @@ -8,7 +8,7 @@ search_tools: - search_tool_name: "my-perplexity-search" litellm_params: search_provider: "perplexity" - # Alternative provider example (requires YDC_API_KEY): + # Alternative provider example (requires YDC_API_KEY or legacy YOUCOM_API_KEY): # - search_tool_name: "my-you-com-search" # litellm_params: # search_provider: "you_com"