How to connect Zyte API to OpenClaw
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.
Zyte APIAPI KEYMCPExtract data from URLs, scrape pages, and monitor service status. Once connected, OpenClaw can read and act on Zyte API from chat — pairing, token refresh, and tool wiring handled for you.
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.
Copy this prompt into OpenClaw, or open the Zyte API skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Zyte API" (hith3sh/zyte-api-scraping) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/zyte-api-scraping
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Zyte API.
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 Zyte API
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Zyte API?"
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 Zyte API in the ClawLink 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:
npx -y @useclawlink/cli loginlogin 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.
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, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Zyte API integration 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 |
Try it: find the Zyte API tool you need
Browse the 7 Zyte API tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Zyte API to active scheduled maintenances and walk me through the result in plain English.
Use Zyte API to components and walk me through the result in plain English.
Use Zyte API to extract zyte api and walk me through the result in plain English.
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 comparison.
Troubleshooting
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.
FAQ
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.
