Repository navigation
feat(web-search): add Keenable as an external search backend - #238
Open
KGKallasmaa wants to merge 1 commit into
Open
KGKallasmaa wants to merge 1 commit into
KGKallasmaa wants to merge 1 commit into
Conversation
Signed-off-by: KGKallasmaa <KGKallasmaa@users.noreply.github.com>
Owner
|
Thanks for the PR, and for disclosing that you work with the Keenable team. DreamCoder adds commercial services, such as provider presets or search backends, through its sponsorship program rather than as regular contributions. If Keenable is interested, please email diaoshengjia@gmail.com with a short introduction and your budget, and we can go over the options there. We'll keep this PR on hold until then. |
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
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.
Summary
Adds Keenable as a third external WebSearch backend, after Tavily and Brave.
webSearch.mode: 'keenable'andwebSearch.keenableApiKeyin settings, added to the zod schema and the resolver.automode, and as the fallback when native Anthropic search fails, the order is Tavily, then Brave, then Keenable. Existing setups don't change.searchWithKeenablecallsPOST https://api.keenable.ai/v1/searchwithX-API-Key, sends{ query, max_results: 8 }and mapsresults[]to{ title, url }, the same way as the other backends. Domain filters go in assite:clauses, the same as Brave.backend.test.ts.Disclosure: I work with the Keenable team.
cc @GoDiao