LangChain + Pinecone + NextJS Integration

LangChain + Pinecone + NextJS Integration

Our client is a workforce analytics consultant who compiled a folder with past research, notes, PDF’s, statistics, and URL’s on workforce data.


The client needed to generate reports for their clients, but was manually CMD+F through the folder for relevant results and including it in their reports. This process was time-consuming, and they wanted a way to query their database using ChatGPT to get the stats they needed. They also wanted to use this tool to generate job recommendations for their clients.


This project was a partnership between Chao Wu and Michael Lin, who advised this project.

Chatbot Components

The tool consisted of 3 main parts:

  • The chatbot that the client could ask questions to
  • An admin panel for uploading files and URL's for context
  • A dashboard for managing the uploaded context

The front end was built using one of the AI Chatbot templates provided by Vercel.

The backend tool we built used a combination of Langchain API’s for processing the various file types as context and PineconeDB for storing embeddings.


Screenshots are below:



Screen Shot 2023-07-18 at 9.40.47 PM.png



Admin Panel






Screen Shot 2023-07-18 at 9.44.27 PM.png

How the Tool Works

The flow for this tool is as follows:


  1. The client uploads all of their context using the admin panel we built for them
  2. We store these embeddings into PineCone, a vector DB
  3. When the customer asks a query, we first turn their query into a vector, and run a vector comparison within PineCone DB to find vectors that are most similar as context.
  4. We return all vectors over the threshold we set for a similarity match
  5. We then augment their query with our own prompts & additional LLM chaining if needed to be more specific about the kind of response we are looking for
  6. We return the result.


Key Insights

URL Handling

When it comes to handling URL's for context, the client had a common misconception that we could just pass ChatGPT a URL in a prompt, and it would parse the website's content for us.


This is actually incorrect. For example, if you ask it, “Give me the data from <insert url> about how much a teacher makes per year”, and it returns the right data, it’s often just a coincidence that the data it returns is the same from the website.


It could also be that that website was part of the initial training set for ChatGPT, hence why it returns the same response.


However, it did NOT actually crawl the website in real-time to return that response.


One way to prove this is if you ask it a query like: “Summarize this story:"


ChatGPT will actually return a summary, even though if you go to that website, it actually leads to a 404.


To get around this, you have to use web scraping API’s to access the content of a URL first, and then pass that text as context to ChatGPT.


And then even after scraping the data, you often have to “clean” the data because as is, it may contain unnecessary tags or is poorly formatted, which makes it harder for ChatGPT to understand. 


Fortunately, LangChain has API’s where you can pass in URL’s that handle this pre-processing for you, that should be used instead.

Data Privacy

Client also asked a question about whether or not the context they passed into OpenAI will be used to train OpenAI’s models or not.


As of March 1st, 2023, Open AI has made it clear in their TOS that data passed through their API will NOT be used in their training set


The data is only retained to monitor for abuse for 30 days, after which it is deleted.


However, the data passed to non-API consumer services like ChatGPT or Dall-E MAY be used to improve their models.


It is possible to request to opt out of this for ChatGPT by turning off Chat History.



You can see a screenshot of their API data usage policy as of 7/18/23:

Screen Shot 2023-07-18 at 10.00.21 PM.png


Relevant data policy links:

1. OpenAI Data Usage Policy

2. Turning off Chat History opts out of training




Need your own ChatGPT bot built?


We will build your Chatbot in 2 months. Reach out to us at