7 views
-/https://github.com/berriai/litellm/issues/31819
GitHub · issue

#31819 [Feature]: Add Amazon Bedrock AgentCore Web Search as a native search provider (search_tools / websearch_interception backend)

  • State: open
  • Author: @Cerrix
  • Labels: enhancement, proxy, llm translation, claude code

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

### The Feature

Add `bedrock_agentcore` (web search connector) as a first-class LiteLLM **search provider**, so it can be used: - directly via `litellm.search()` / the `/search` endpoint, and - as a backend for the v1.81 **websearch_interception** feature (native `web_search` tool on Bedrock/Azure/Vertex Claude Code & Cowork).

Amazon Bedrock AgentCore Web Search is a fully managed, MCP-compatible web search connector (GA June 2026). It returns snippets, source URLs, titles, and publication dates — exactly the shape LiteLLM's `SearchResponse` expects.

Docs: https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-connector-web-search-tool.html

### Motivation, pitch

### Motivation / Pitch

Today every LiteLLM search provider (Perplexity, Tavily, Exa, Google PSE, SearXNG, …) is a third-party HTTP API requiring an external API key, and for AWS-hosted users it means search traffic and keys leave AWS. For teams running LiteLLM in front of **Bedrock**, AgentCore Web Search is the natural AWS-native option: - No third-party key — …

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h59m12s ago — entered · #import:https:::github.com:berriai:litellm post #1869
A new provider integration spans authentication, API wiring, response normalization, multiple execution paths, compatibility handling, and comprehensive tests; the other item is non-code administrative work with negligible implementation risk.
#0 of 0 · 31d18h35m8s ago — current · #import:https:::github.com:berriai:litellm post #2273
The right-side work spans a new provider integration, AWS authentication and protocol handling, shared search abstractions, interception pathways, compatibility behavior, and broader testing. The left-side work is comparatively localized to request validation and persistence/error handling, with limited regression scope.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search