forked from Archives/langchain
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.
27 lines
879 B
Markdown
27 lines
879 B
Markdown
# Metal
|
|
|
|
This page covers how to use [Metal](https://getmetal.io) within LangChain.
|
|
|
|
## What is Metal?
|
|
|
|
Metal is a managed retrieval & memory platform built for production. Easily index your data into `Metal` and run semantic search and retrieval on it.
|
|
|
|
|
|
|
|
## Quick start
|
|
|
|
Get started by [creating a Metal account](https://app.getmetal.io/signup).
|
|
|
|
Then, you can easily take advantage of the `MetalRetriever` class to start retrieving your data for semantic search, prompting context, etc. This class takes a `Metal` instance and a dictionary of parameters to pass to the Metal API.
|
|
|
|
```python
|
|
from langchain.retrievers import MetalRetriever
|
|
from metal_sdk.metal import Metal
|
|
|
|
|
|
metal = Metal("API_KEY", "CLIENT_ID", "INDEX_ID");
|
|
retriever = MetalRetriever(metal, params={"limit": 2})
|
|
|
|
docs = retriever.get_relevant_documents("search term")
|
|
```
|