[PR #627] [MERGED] Perigon integration #872

Closed
opened 2026-02-17 17:21:17 -05:00 by yindo · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/627
Author: @ipenywis
Created: 9/23/2025
Status: Merged
Merged: 9/25/2025
Merged by: @lnhsingh

Base: mainHead: perigon-integration


📝 Commits (4)

  • 43b07cb feat: add langchain-perigon integration documentation
  • d2ea685 feat: add proper error handling to the code snippets
  • a3100a5 fix: remove integration with langchain section
  • 774fc12 fix: reorder perigon card in alphabetical order

📊 Changes

4 files changed (+414 additions, -0 deletions)

View changed files

📝 src/oss/python/integrations/providers/all_providers.mdx (+8 -0)
📝 src/oss/python/integrations/providers/index.mdx (+1 -0)
src/oss/python/integrations/providers/perigon.mdx (+80 -0)
src/oss/python/integrations/retrievers/perigon.mdx (+325 -0)

📄 Description

Overview

Add the documentation for the new perigon-langchain integration. The Perigon API suite provides fast, structured access to global news and events, helping you build real-time, data-driven products. Whether you're tracking emerging risks, surfacing relevant articles, or uncovering key insights, Perigon gives you the tools to do it programmatically.

Type of change

Type: New documentation page

Related issues/PRs

  • GitHub issue:
  • Feature PR:
  • Linear issue:
  • Slack thread:

Checklist

  • I have read the contributing guidelines
  • I have tested my changes locally using docs dev
  • All code examples have been tested and work correctly
  • I have used root relative paths for internal links
  • I have updated navigation in src/docs.json if needed
  • I have gotten approval from the relevant reviewers
  • (Internal team members only / optional) I have created a preview deployment using the Create Preview Branch workflow

Additional notes

You can learn more about Perigon from the following links:

  1. Perigon workspace: https://perigon.io
  2. Perigon for developers: https://dev.perigon.io

🔄 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/627 **Author:** [@ipenywis](https://github.com/ipenywis) **Created:** 9/23/2025 **Status:** ✅ Merged **Merged:** 9/25/2025 **Merged by:** [@lnhsingh](https://github.com/lnhsingh) **Base:** `main` ← **Head:** `perigon-integration` --- ### 📝 Commits (4) - [`43b07cb`](https://github.com/langchain-ai/docs/commit/43b07cbb2b4baafbb9ecd7b71f782890bac5ee57) feat: add langchain-perigon integration documentation - [`d2ea685`](https://github.com/langchain-ai/docs/commit/d2ea6857c198bae8051701fb06c7e6f60d6f3c05) feat: add proper error handling to the code snippets - [`a3100a5`](https://github.com/langchain-ai/docs/commit/a3100a54bc353ce35dad8d0ed9635680fc670ff9) fix: remove integration with langchain section - [`774fc12`](https://github.com/langchain-ai/docs/commit/774fc1249e260cb509c67b56d875f98b73f693ae) fix: reorder perigon card in alphabetical order ### 📊 Changes **4 files changed** (+414 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/oss/python/integrations/providers/all_providers.mdx` (+8 -0) 📝 `src/oss/python/integrations/providers/index.mdx` (+1 -0) ➕ `src/oss/python/integrations/providers/perigon.mdx` (+80 -0) ➕ `src/oss/python/integrations/retrievers/perigon.mdx` (+325 -0) </details> ### 📄 Description ## Overview <!-- Brief description of what documentation is being added/updated --> Add the documentation for the new [perigon-langchain](https://github.com/goperigon/langchain-perigon) integration. The Perigon API suite provides fast, structured access to global news and events, helping you build real-time, data-driven products. Whether you're tracking emerging risks, surfacing relevant articles, or uncovering key insights, Perigon gives you the tools to do it programmatically. ## Type of change **Type:** New documentation page ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> You can learn more about Perigon from the following links: 1. Perigon workspace: https://perigon.io 2. Perigon for developers: https://dev.perigon.io --- <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-02-17 17:21:17 -05:00
yindo closed this issue 2026-02-17 17:21:17 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#872