# How to connect Benzinga to OpenClaw (paste one key, 10 tools) > Connect Benzinga to OpenClaw with ClawLink: paste your Benzinga key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/benzinga The usual route to Benzinga 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 Benzinga setup: install one ClawHub skill, connect Benzinga in the browser, and OpenClaw can call real Benzinga 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 Benzinga. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Benzinga** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect benzinga # connect Benzinga (browser OAuth) npx -y @useclawlink/cli actions benzinga # list available actions npx -y @useclawlink/cli run benzinga --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Benzinga in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Benzinga API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Benzinga, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Benzinga is connected in the dashboard, that agent calls the same 10 Benzinga tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Benzinga MCP for OpenClaw Looking for a Benzinga MCP server for OpenClaw? ClawLink connects Benzinga to OpenClaw and exposes 10 Benzinga tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Benzinga integration](https://claw-link.dev/hermes/benzinga) works the same way. ## What the OpenClaw Benzinga integration can do 10 Benzinga tools are ready for OpenClaw once the account is connected. ### All 10 Benzinga tools for OpenClaw | Tool | What it does | |---|---| | **Get calendar earnings stream** `benzinga_get_calendar_earnings_stream` | Subscribe to real-time earnings calendar events via WebSocket | | **Get conference calls v21** `benzinga_get_conference_calls_v21` | Retrieve conference call data for a selected period and/or security using v2.1 API | | **Get consensus ratings** `benzinga_get_consensus_ratings` | Get aggregated consensus analyst ratings and price targets for a stock ticker | | **Get earnings v21** `benzinga_get_earnings_v21` | Retrieve earnings calendar data (v2.1) | | **Get economics v21** `benzinga_get_economics_v21` | Retrieve economic calendar data including indicators, releases, and reports from various | | **Get news channels** `benzinga_get_news_channels` | Retrieve all available news channels that can be used to filter news items | | **Get newsfeed stream** `benzinga_get_newsfeed_stream` | Get WebSocket connection details for real-time Benzinga newsfeed streaming | | **Get ratings v21** `benzinga_get_ratings_v21` | Fetch analyst ratings data including upgrades, downgrades, initiations, and price target | | **Get removed news** `benzinga_get_removed_news` | Retrieves IDs and timestamps of news articles that have been removed from Benzinga's database | | **Get removed v21** `benzinga_get_removed_v21` | Retrieve removed or cancelled calendar events from Benzinga (v2.1) | ## Example prompts **Get Calendar Earnings Stream** > Pull the relevant data from Benzinga, summarize it in plain English, and point out anything that needs attention. **Get Conference Calls V21** > Pull the relevant data from Benzinga, summarize it in plain English, and point out anything that needs attention. **Get Consensus Ratings** > Pull the relevant data from Benzinga, summarize it in plain English, and point out anything that needs attention. **Get Earnings V21** > Pull the relevant data from Benzinga, 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 Benzinga working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Benzinga API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Benzinga 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 Benzinga. | 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 Benzinga actions to the runtime in a format your agent can reliably use. | 10 tools for Benzinga are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Benzinga 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 Benzinga in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Benzinga key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Benzinga skill but can't call the tools The ClawHub skill teaches OpenClaw about Benzinga, but the calls run through the ClawLink plugin and your connected account. Make sure Benzinga 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 Benzinga 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 Benzinga tools Benzinga 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 Benzinga 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. ### Benzinga 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 Benzinga has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Benzinga integration? Yes. ClawLink is the fastest way to connect OpenClaw to Benzinga: link your Benzinga account once in the browser and OpenClaw can call the Benzinga API through 10 ready-made tools — no custom code or token handling. ### How do I add Benzinga to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Benzinga skill from ClawHub, then you click Connect in the dashboard to authorize Benzinga. OpenClaw calls the tools from the next message — no config files, and the Benzinga key you paste is stored server-side instead of in your environment. ### How long does it take to connect Benzinga to OpenClaw? About two minutes. Sign in, click Connect next to Benzinga in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Benzinga 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 Benzinga working from chat. ### OpenClaw installed the Benzinga skill but can't call the tools The ClawHub skill teaches OpenClaw about Benzinga, but the calls run through the ClawLink plugin and your connected account. Make sure Benzinga 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](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [Connect DataforSEO](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [OpenClaw Metabase integration](https://claw-link.dev/openclaw/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.