mirror of
https://github.com/hwchase17/langchain
synced 2024-10-29 17:07:25 +00:00
e2d7677526
# Docs: compound ecosystem and integrations **Problem statement:** We have a big overlap between the References/Integrations and Ecosystem/LongChain Ecosystem pages. It confuses users. It creates a situation when new integration is added only on one of these pages, which creates even more confusion. - removed References/Integrations page (but move all its information into the individual integration pages - in the next PR). - renamed Ecosystem/LongChain Ecosystem into Integrations/Integrations. I like the Ecosystem term. It is more generic and semantically richer than the Integration term. But it mentally overloads users. The `integration` term is more concrete. UPDATE: after discussion, the Ecosystem is the term. Ecosystem/Integrations is the page (in place of Ecosystem/LongChain Ecosystem). As a result, a user gets a single place to start with the individual integration.
26 lines
761 B
Markdown
26 lines
761 B
Markdown
# Databerry
|
|
|
|
This page covers how to use the [Databerry](https://databerry.ai) within LangChain.
|
|
|
|
## What is Databerry?
|
|
|
|
Databerry is an [open source](https://github.com/gmpetrov/databerry) document retrievial platform that helps to connect your personal data with Large Language Models.
|
|
|
|
|
|
|
|
## Quick start
|
|
|
|
Retrieving documents stored in Databerry from LangChain is very easy!
|
|
|
|
```python
|
|
from langchain.retrievers import DataberryRetriever
|
|
|
|
retriever = DataberryRetriever(
|
|
datastore_url="https://api.databerry.ai/query/clg1xg2h80000l708dymr0fxc",
|
|
# api_key="DATABERRY_API_KEY", # optional if datastore is public
|
|
# top_k=10 # optional
|
|
)
|
|
|
|
docs = retriever.get_relevant_documents("What's Databerry?")
|
|
```
|