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.
631 B
631 B
Anyscale
This page covers how to use the Anyscale ecosystem within LangChain. It is broken into two parts: installation and setup, and then references to specific Anyscale wrappers.
Installation and Setup
- Get an Anyscale Service URL, route and API key and set them as environment variables (
ANYSCALE_SERVICE_URL
,ANYSCALE_SERVICE_ROUTE
,ANYSCALE_SERVICE_TOKEN
). - Please see the Anyscale docs for more details.
Wrappers
LLM
There exists an Anyscale LLM wrapper, which you can access with
from langchain.llms import Anyscale