langchain - 💡(How to fix) Fix Add Perplexity embedding models [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langchain-ai/langchain#36726Fetched 2026-04-16 06:35:50
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×3issue_type_added ×1
RAW_BUFFERClick to expand / collapse

Checked other resources

  • This is a feature request, not a bug report or usage question.
  • I added a clear and descriptive title that summarizes the feature request.
  • I used the GitHub search to find a similar feature request and didn't find it.
  • I checked the LangChain documentation and API reference to see if this feature already exists.
  • This is not related to the langchain-community package.

Package (Required)

  • langchain
  • langchain-openai
  • langchain-anthropic
  • langchain-classic
  • langchain-core
  • langchain-model-profiles
  • langchain-tests
  • langchain-text-splitters
  • langchain-chroma
  • langchain-deepseek
  • langchain-exa
  • langchain-fireworks
  • langchain-groq
  • langchain-huggingface
  • langchain-mistralai
  • langchain-nomic
  • langchain-ollama
  • langchain-openrouter
  • langchain-perplexity
  • langchain-qdrant
  • langchain-xai
  • Other / not sure / general

Feature Description

I am proposing native support for Perplexity embedding models within the langchain-perplexity module. This integration would enable users to build end-to-end RAG agents exclusively powered by Perplexity services.

Use Case

Currently, developers must manually implement a PerplexityEmbeddings class to build a RAG agent using Perplexity services. Integrating this feature directly into LangChain would significantly streamline the process.

Proposed Solution

A PerplexityEmbeddings class can be implemented within langchain_perplexity.embeddings, mirroring the standard structure of other LangChain embeddings. This implementation leverages the perplexityai SDK to handle service interactions.

Alternatives Considered

No response

Additional Context

No response

extent analysis

TL;DR

Implement a PerplexityEmbeddings class within the langchain_perplexity.embeddings module to provide native support for Perplexity embedding models.

Guidance

  • Review the perplexityai SDK documentation to understand how to handle service interactions for Perplexity embedding models.
  • Consider the standard structure of other LangChain embeddings to ensure consistency in the implementation of the PerplexityEmbeddings class.
  • Evaluate the feasibility of integrating the proposed PerplexityEmbeddings class with existing RAG agents in LangChain.
  • Investigate potential dependencies or requirements for the langchain-perplexity module to support the new embedding model.

Example

No example code is provided due to the lack of specific implementation details in the issue.

Notes

The proposed solution assumes that the perplexityai SDK is compatible with the LangChain framework and that the necessary dependencies are available.

Recommendation

Apply workaround: Implement the proposed PerplexityEmbeddings class within the langchain_perplexity.embeddings module, as this would provide native support for Perplexity embedding models and streamline the process for developers.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING