langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-21 20:05:30 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #3821] [MERGED] docs(deepagents): align Perplexity env var with PERPLEXITY_API_KEY #3839

New Issue
Closed
opened 2026-06-05 18:53:19 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 18:53:19 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/3821
Author: @jliounis
Created: 4/30/2026
Status: ✅ Merged
Merged: 5/8/2026
Merged by: @mdrxy

Base: main ← Head: docs-perplexity-env-var-alignment

📝 Commits (1)

  • ec09caa docs(deepagents): align Perplexity env var with PERPLEXITY_API_KEY

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 src/oss/deepagents/cli/providers.mdx (+1 -1)

📄 Description

Summary

Updates the Deep Agents CLI providers table to surface PERPLEXITY_API_KEY as the canonical Perplexity environment variable, with PPLX_API_KEY listed as a fallback for backwards compatibility.

This aligns the published docs page (https://docs.langchain.com/oss/python/deepagents/cli/providers) with the upstream code change in langchain-ai/deepagents#3061, which switches the canonical entry in PROVIDER_API_KEY_ENV from PPLX_API_KEY to PERPLEXITY_API_KEY while preserving PPLX_API_KEY as a fallback. Without this docs change, the providers table will be inconsistent with the shipped CLI behavior the moment #3061 merges.

PERPLEXITY_API_KEY is the canonical name per the official Perplexity API docs; PPLX_API_KEY remains supported so existing users are not broken.

This is a follow-up to two recently merged Perplexity docs PRs in this repo: #3798 (Perplexity Search retriever/tool) and #3806 (PerplexityEmbeddings).

Testing

  • Single-line edit to src/oss/deepagents/cli/providers.mdx; rendered table cell now reads `PERPLEXITY_API_KEY` (or `PPLX_API_KEY`).
  • No other rows or files touched.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/3821 **Author:** [@jliounis](https://github.com/jliounis) **Created:** 4/30/2026 **Status:** ✅ Merged **Merged:** 5/8/2026 **Merged by:** [@mdrxy](https://github.com/mdrxy) **Base:** `main` ← **Head:** `docs-perplexity-env-var-alignment` --- ### 📝 Commits (1) - [`ec09caa`](https://github.com/langchain-ai/docs/commit/ec09caa4870fc03b390b4736d0c011783030e998) docs(deepagents): align Perplexity env var with PERPLEXITY_API_KEY ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/oss/deepagents/cli/providers.mdx` (+1 -1) </details> ### 📄 Description ## Summary Updates the Deep Agents CLI providers table to surface `PERPLEXITY_API_KEY` as the canonical Perplexity environment variable, with `PPLX_API_KEY` listed as a fallback for backwards compatibility. This aligns the published docs page (https://docs.langchain.com/oss/python/deepagents/cli/providers) with the upstream code change in [langchain-ai/deepagents#3061](https://github.com/langchain-ai/deepagents/pull/3061), which switches the canonical entry in `PROVIDER_API_KEY_ENV` from `PPLX_API_KEY` to `PERPLEXITY_API_KEY` while preserving `PPLX_API_KEY` as a fallback. Without this docs change, the providers table will be inconsistent with the shipped CLI behavior the moment #3061 merges. `PERPLEXITY_API_KEY` is the canonical name per the official [Perplexity API docs](https://docs.perplexity.ai); `PPLX_API_KEY` remains supported so existing users are not broken. This is a follow-up to two recently merged Perplexity docs PRs in this repo: #3798 (Perplexity Search retriever/tool) and #3806 (PerplexityEmbeddings). ## Testing - Single-line edit to `src/oss/deepagents/cli/providers.mdx`; rendered table cell now reads `` `PERPLEXITY_API_KEY` (or `PPLX_API_KEY`) ``. - No other rows or files touched. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 18:53:19 -04:00
yindo closed this issue 2026-06-05 18:53:19 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#3839
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?