How to connect Screenshot API to OpenClaw
Connect Screenshot API to OpenClaw with ClawLink: paste your Screenshot API key once and 5 tools work from chat. No MCP server to run, nothing stored on your machine.
Screenshot APIAPI KEYMCPScreenshot API renders webpages and custom HTML as images, PDFs, videos, or extracted content and supports paid asynchronous bulk capture jobs.. Once connected, OpenClaw can read and act on Screenshot API from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Screenshot 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 Screenshot API setup: install one ClawHub skill, connect Screenshot API in the browser, and OpenClaw can call real Screenshot API 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 Screenshot 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 Screenshot API
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Screenshot 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 Screenshot API in the ClawLink dashboard — paste your Screenshot API API key once.
Verify the connection by asking OpenClaw:
Use Screenshot API to download bulk results 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 Screenshot API is connected in the dashboard, that agent calls the same 5 Screenshot API tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Screenshot API MCP for OpenClaw
Looking for a Screenshot API MCP server for OpenClaw? ClawLink connects Screenshot API to OpenClaw and exposes 5 Screenshot API tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Screenshot API integration works the same way.
What the OpenClaw Screenshot API integration can do
5 Screenshot API tools are ready for OpenClaw once the account is connected.
All 5 Screenshot API tools for OpenClaw
| Tool | What it does |
|---|---|
Download bulk results screenshot_api_download_bulk_results | Download the processed result CSV for a completed paid bulk screenshot job UUID |
Get bulk job status screenshot_api_get_bulk_job_status | Get progress and success/failure counts for a paid asynchronous bulk screenshot job UUID |
Create bulk CSV job screenshot_api_create_bulk_csv_job | Upload a CSV file to start a paid asynchronous bulk screenshot job and return the provider's |
Create bulk json job screenshot_api_create_bulk_json_job | Start a paid asynchronous bulk screenshot job from up to 50 JSON request items and return the |
Render screenshot screenshot_api_render_screenshot | Render a webpage or custom HTML and return a stored image, PDF, or video URL plus optional |
Try it: find the Screenshot API tool you need
Browse the 5 Screenshot API tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Screenshot API to download bulk results and walk me through the result in plain English.
Pull the relevant data from Screenshot API, summarize it in plain English, and point out anything that needs attention.
Create it in Screenshot API for me, then confirm the important fields before you finish.
Create it in Screenshot API for me, then confirm the important fields before you finish.
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 Screenshot API working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Screenshot API API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Screenshot 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 Screenshot 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 Screenshot API actions to the runtime in a format your agent can reliably use. | 5 tools for Screenshot API are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Screenshot 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 Screenshot API in the browser, and the 5 tools above work from chat. There is no SDK and no config file, and the Screenshot 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 Screenshot API skill but can't call the tools
The ClawHub skill teaches OpenClaw about Screenshot API, but the calls run through the ClawLink plugin and your connected account. Make sure Screenshot 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 Screenshot 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 Screenshot API tools
Screenshot 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 Screenshot 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.
Screenshot 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 Screenshot 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 Screenshot API integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Screenshot API: link your Screenshot API account once in the browser and OpenClaw can call the Screenshot API API through 5 ready-made tools — no custom code or token handling.
How do I add Screenshot API to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Screenshot API skill from ClawHub, then you click Connect in the dashboard to authorize Screenshot API. OpenClaw calls the tools from the next message — no config files, and the Screenshot API key you paste is stored server-side instead of in your environment.
How long does it take to connect Screenshot API to OpenClaw?
About two minutes. Sign in, click Connect next to Screenshot API in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Screenshot 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 Screenshot API working from chat.
OpenClaw installed the Screenshot API skill but can't call the tools
The ClawHub skill teaches OpenClaw about Screenshot API, but the calls run through the ClawLink plugin and your connected account. Make sure Screenshot 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
OpenClaw GitHub integration
Manage repositories, issues, pull requests, and workflows
Connect PagerDuty
Manage incidents, on-call schedules, and services
SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.