{{ message }}
Repository navigation
feat: support configurable Serper-compatible search endpoints - #4079
Open
litescraper wants to merge 1 commit into
Open
litescraper wants to merge 1 commit into
litescraper wants to merge 1 commit into
Conversation
github-actions
Bot
added
the
type:documentation
Contributor
|
Heads-up for maintainers This PR is from a fork and touches integrations whose integration tests require API keys. Affected integrations:
Please run the integration tests locally ( |
Contributor
Coverage report (serperdev)
Click to see where and how coverage changedThis report was generated by python-coverage-comment-action |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Related Issues
None.
Proposed Changes
Allow Haystack users to choose a Serper-compatible search provider without modifying component source code. This lets users select a provider that fits their budget or deployment requirements.
Set
SERPERDEV_BASE_URLto the provider’s base URL and configureSERPERDEV_API_KEY. The component removes trailing slashes and appends/search. Both synchronous and asynchronous searches use the configured endpoint.Support any Serper.dev-compatible endpoint (like litescrape.com, serpbase.dev, serpensapi.org, and others).
When the setting is omitted, the component continues using its existing Serper endpoint. Authentication, request payloads, timeouts, and result processing remain unchanged.
How did you test it?
Notes for the reviewer
The change is limited to endpoint selection and its documentation. No tests were added.