docs: add Linkup integration documentation #28366
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
cjumel
force-pushed
the
cj/doc
branch
2 times, most recently
from
3ca81de to
1440900
Compare
BruceWouaigne
approved these changes
Nov 27, 2024
dosubot
bot
added
size:XL
|
Hi @efriis, gentle reminder that it would be great if you had time to take a look at this PR 🙂 |
efriis
approved these changes
Dec 9, 2024
dosubot
bot
added
the
lgtm
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.
Description
First of all, thanks for the great framework that is LangChain!
At Linkup we're working on an API to connect LLMs and agents to the internet and our partner sources. We'd be super excited to see our API integrated in LangChain! This essentially consists in adding a LangChain retriever and tool, which is done in our own package. Here we're simply following the integration documentation and update the documentation of LangChain to mention the Linkup integration.
We do have tests (both units & integration) in our source code, and tried to follow as close as possible the integration documentation which specifically requests to focus on documentation changes for an integration PR, so I'm not adding tests here, even though the PR checklist seems to suggest so. Feel free to correct me if I got this wrong!
By the way, we would be thrilled by being mentioned in the list of providers which have standalone packages here, is there something in particular for us to do for that? 🙂
Twitter handle
Linkup_platform