# How to connect Zyte API to OpenClaw (paste one key, 7 tools) > Connect Zyte API to OpenClaw with ClawLink: paste your Zyte API key once and 7 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/zyte-api The usual route to Zyte API 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 Zyte API setup: install one ClawHub skill, connect Zyte API in the browser, and OpenClaw can call real Zyte API actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/zyte-api ## Setup It takes three steps to connect OpenClaw to Zyte API. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Zyte API** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **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 zyte-api # connect Zyte API (browser OAuth) npx -y @useclawlink/cli actions zyte-api # list available actions npx -y @useclawlink/cli run zyte-api --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 Zyte API in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Zyte API API key once. Verify the connection by asking OpenClaw: > Use Zyte API to active scheduled maintenances and walk me through the result in plain English. ### 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 Zyte API is connected in the dashboard, that agent calls the same 7 Zyte API 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). ## Zyte API MCP for OpenClaw Looking for a Zyte API MCP server for OpenClaw? ClawLink connects Zyte API to OpenClaw and exposes 7 Zyte API 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 Zyte API integration](https://claw-link.dev/hermes/zyte-api) works the same way. ## What the OpenClaw Zyte API integration can do 7 Zyte API tools are ready for OpenClaw once the account is connected. ### All 7 Zyte API tools for OpenClaw | Tool | What it does | |---|---| | **Active scheduled maintenances** `zyte_api_active_scheduled_maintenances` | Get active maintenances | | **Components** `zyte_api_components` | Get Zyte service component statuses | | **Extract zyte API** `zyte_api_extract_zyte_api` | Extract data from a URL using Zyte API | | **Get scheduled maintenances** `zyte_api_get_scheduled_maintenances` | Get scheduled maintenances | | **Get unresolved incidents** `zyte_api_get_unresolved_incidents` | Get unresolved incidents | | **List incidents** `zyte_api_list_incidents` | List recent Zyte incidents | | **Status** `zyte_api_status` | Get Zyte API operational status | ## Example prompts **Active Scheduled Maintenances** > Use Zyte API to active scheduled maintenances and walk me through the result in plain English. **Components** > Use Zyte API to components and walk me through the result in plain English. **Extract Zyte Api** > Use Zyte API to extract zyte api and walk me through the result in plain English. **Get Scheduled Maintenances** > Pull the relevant data from Zyte API, 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 Zyte API working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Zyte API API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Zyte API 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 Zyte API. | 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 Zyte API actions to the runtime in a format your agent can reliably use. | 7 tools for Zyte API are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Zyte API 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 Zyte API in the browser, and the 7 tools above work from chat. There is no SDK and no config file, and the Zyte API 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 Zyte API skill but can't call the tools The ClawHub skill teaches OpenClaw about Zyte API, but the calls run through the ClawLink plugin and your connected account. Make sure Zyte API 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 Zyte API 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 Zyte API tools Zyte API 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 Zyte API 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. ### Zyte API 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 Zyte API has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Zyte API integration? Yes. ClawLink is the fastest way to connect OpenClaw to Zyte API: link your Zyte API account once in the browser and OpenClaw can call the Zyte API API through 7 ready-made tools — no custom code or token handling. ### How do I add Zyte API to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Zyte API skill from ClawHub, then you click Connect in the dashboard to authorize Zyte API. OpenClaw calls the tools from the next message — no config files, and the Zyte API key you paste is stored server-side instead of in your environment. ### How long does it take to connect Zyte API to OpenClaw? About two minutes. Sign in, click Connect next to Zyte API in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Zyte API 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 Zyte API working from chat. ### OpenClaw installed the Zyte API skill but can't call the tools The ClawHub skill teaches OpenClaw about Zyte API, but the calls run through the ClawLink plugin and your connected account. Make sure Zyte API 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 - [PostHog tools](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [OpenClaw DataforSEO integration](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase](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.