langchain-ai/langchain

Add Perplexity cost tracking

Open

#31,647 建立於 2025年4月14日

在 GitHub 查看
 (6 留言) (1 反應) (1 負責人)Python (136,758 star) (22,617 fork)batch import
externalhelp wantedintegrationinvestigateperplexity

描述

Issue you'd like to raise.

costs shown on langsmith for perplexity API calls are inaccurate (even upto an order of magnitude). refer to their docs for how to calculate costs: https://docs.perplexity.ai/guides/models/sonar-reasoning-pro#detailed-pricing-breakdown-for-sonar-reasoning-pro

The problem is that pplx cost depends not only on input and output tokens but also on search queries and

Suggestion:

either add support for calculating this within langsmith platform or let users update the true cost while tracing an LLM call.

貢獻者指南

技術棧
python
領域
backendanalytics
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic PythonLangChain framework basicsAPI cost model understanding
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
Review the Perplexity API pricing documentation to understand the cost formula (input tokens, output tokens, search queries). Examine the LangChain callback system (e.g., `libs/langchain/langchain/callbacks/tracers/`) for existing cost tracking logic. Check issue comments for maintainer input or assignee progress. Consider extending the LangSmith tracing client or adding a per call cost override.