feat(web-search): add keyless Parallel Search fallback - #229
Open
georgeatparallel wants to merge 2 commits into
Open
feat(web-search): add keyless Parallel Search fallback#229georgeatparallel wants to merge 2 commits into
georgeatparallel wants to merge 2 commits into
Conversation
georgeatparallel
marked this pull request as ready for review
August 25, 2026 22:16
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
1 participant
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.
Right now, installing
web-searchisn't enough to actually search the web. Unless you've already signed up for Exa and configuredEXA_API_KEY, the tool fails. That's a lot of setup for something people reasonably expect to work as soon as they install the plugin.This PR keeps Exa exactly as it is for anyone who already uses it. If no Exa key is configured, the plugin falls back to Parallel's free, anonymous Search MCP endpoint instead. No account, API key, or additional configuration required. Existing Exa keys still take priority, and anonymous requests never include credentials.
The fallback keeps the existing
web_searchinterface, enforces requested domain restrictions, reuses a stable session for free-tier rate limiting, and surfaces provider errors clearly. I tested it against the live endpoint and added coverage for both providers, domain filtering, session reuse, malformed responses, and error handling.Verified with 10 passing tests, strict TypeScript checking,
npm run validate, andgit diff --check.