How to connect Perigon to OpenClaw
Connect Perigon to OpenClaw with ClawLink: paste your Perigon key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine.
PerigonAPI KEYMCPPerigon provides an HTTP REST API for retrieving news and web content data, offering structured data suitable for various applications.. Once connected, OpenClaw can read and act on Perigon from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Perigon access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Perigon setup: install one ClawHub skill, connect Perigon in the browser, and OpenClaw can call real Perigon actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Perigon.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Perigon
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Perigon?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Perigon in the ClawLink dashboard — paste your Perigon API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Perigon, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Perigon is connected in the dashboard, that agent calls the same 9 Perigon tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Perigon MCP for OpenClaw
Looking for a Perigon MCP server for OpenClaw? ClawLink connects Perigon to OpenClaw and exposes 9 Perigon tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Perigon integration works the same way.
What the OpenClaw Perigon integration can do
9 Perigon tools are ready for OpenClaw once the account is connected.
All 9 Perigon tools for OpenClaw
| Tool | What it does |
|---|---|
Get articles perigon_get_articles | Retrieve a list of news articles based on filters |
Get companies perigon_get_companies | Retrieve information on companies in Perigon’s entity database |
Get journalists perigon_get_journalists | Retrieve journalist profiles including title, Twitter handle, bio, and location |
Get sources perigon_get_sources | Retrieve a list of media sources with filtering options |
Get stories perigon_get_stories | Retrieve clusters of related articles covering the same event or topic with aggregate metrics |
Get topics perigon_get_topics | Retrieve all available Perigon news topics |
Get wikipedia perigon_get_wikipedia | Search and filter Wikipedia pages |
Vector search articles perigon_vector_search_articles | Perform a vector search on Perigon’s real-time news database |
Vector search wikipedia perigon_vector_search_wikipedia | Perform semantic retrieval of Wikipedia pages using vector search |
Try it: find the Perigon tool you need
Browse the 9 Perigon tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Perigon, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Perigon, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Perigon, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Perigon, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Perigon working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Perigon API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Perigon account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Perigon. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Perigon actions to the runtime in a format your agent can reliably use. | 9 tools for Perigon are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Perigon to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Perigon in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the Perigon key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Perigon skill but can't call the tools
The ClawHub skill teaches OpenClaw about Perigon, but the calls run through the ClawLink plugin and your connected account. Make sure Perigon is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Perigon from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Perigon tools
Perigon tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Perigon call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Perigon returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Perigon has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Perigon integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Perigon: link your Perigon account once in the browser and OpenClaw can call the Perigon API through 9 ready-made tools — no custom code or token handling.
How do I add Perigon to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Perigon skill from ClawHub, then you click Connect in the dashboard to authorize Perigon. OpenClaw calls the tools from the next message — no config files, and the Perigon key you paste is stored server-side instead of in your environment.
How long does it take to connect Perigon to OpenClaw?
About two minutes. Sign in, click Connect next to Perigon in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Perigon up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Perigon working from chat.
OpenClaw installed the Perigon skill but can't call the tools
The ClawHub skill teaches OpenClaw about Perigon, but the calls run through the ClawLink plugin and your connected account. Make sure Perigon is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
OpenClaw PostHog integration
Track user behavior and feature flags
OpenClaw DataforSEO integration
SEO data APIs for keywords, SERP, and site audits
Metabase tools
Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.