mirror of
https://github.com/hwchase17/langchain.git
synced 2025-11-04 02:03:32 +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.
20 lines
491 B
Markdown
20 lines
491 B
Markdown
# PipelineAI
|
|
|
|
This page covers how to use the PipelineAI ecosystem within LangChain.
|
|
It is broken into two parts: installation and setup, and then references to specific PipelineAI wrappers.
|
|
|
|
## Installation and Setup
|
|
|
|
- Install with `pip install pipeline-ai`
|
|
- Get a Pipeline Cloud api key and set it as an environment variable (`PIPELINE_API_KEY`)
|
|
|
|
## Wrappers
|
|
|
|
### LLM
|
|
|
|
There exists a PipelineAI LLM wrapper, which you can access with
|
|
|
|
```python
|
|
from langchain.llms import PipelineAI
|
|
```
|