> For the complete documentation index, see [llms.txt](https://docs.scraperapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scraperapi.com/integrations/llm-integrations/langchain-integration.md).

# LangChain Integration

**LangChain** is an open-source framework used to bridge LLMs with other tools and external data sources, helping create more powerful and versatile AI applications. This allows LLMs to interact with the real world and perform tasks beyond simple text generation.

Combining **LangChain's** framework with **ScraperAPI** enables AI agents to browse and extract real-time data from the web uninterrupted, bypassing any bot detection systems in place.

When integrated with **LangChain**, `ScraperAPI` complements its capabilities by offering a powerful stack of features, that are invaluable when working with LLMs. These features enable users to:

* **Scrape Webpages** - Web access is critical for AI agents to perform various tasks.
* **Data Formatting:**\
  **-** Generate well-formatted and organized markdown content directly from webpage data to improve LLM performance.\
  **-** Get structured JSON output from certain sites, like Google Search and Amazon Listings Search.
* **Bot Protection Handling** - Bypass CAPTCHAs and scrape complex or heavily protected websites.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scraperapi.com/integrations/llm-integrations/langchain-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.