How to connect TruthScan to OpenClaw
Connect TruthScan to OpenClaw with ClawLink: paste your TruthScan key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine.
TruthScanAPI KEYMCPTruthScan detects AI-generated and manipulated content in images, text, PDFs, video, and audio.. Once connected, OpenClaw can read and act on TruthScan from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to TruthScan 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 TruthScan setup: install one ClawHub skill, connect TruthScan in the browser, and OpenClaw can call real TruthScan 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 TruthScan.
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 TruthScan
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with TruthScan?"
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 TruthScan in the ClawLink dashboard — paste your TruthScan API key once.
Verify the connection by asking OpenClaw:
Use TruthScan to check credits 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 TruthScan is connected in the dashboard, that agent calls the same 8 TruthScan tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
TruthScan MCP for OpenClaw
Looking for a TruthScan MCP server for OpenClaw? ClawLink connects TruthScan to OpenClaw and exposes 8 TruthScan tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes TruthScan integration works the same way.
What the OpenClaw TruthScan integration can do
8 TruthScan tools are ready for OpenClaw once the account is connected.
All 8 TruthScan tools for OpenClaw
| Tool | What it does |
|---|---|
Check credits truthscan_check_credits | Return the connected TruthScan account's remaining detection credits from the canonical image |
Download image asset truthscan_download_image_asset | Download a generated preview or heatmap for an owned TruthScan image detection job |
Get detection result truthscan_get_detection_result | Get the current result of an existing image, text, PDF, video, or audio detection job |
Analyze audio truthscan_analyze_audio | Analyze exactly one public audio URL or uploaded audio/media file for AI generation |
Analyze image truthscan_analyze_image | Submit an image URL for AI-generation detection and, by default, wait for the asynchronous |
Analyze PDF truthscan_analyze_pdf | Submit a publicly reachable PDF URL for asynchronous tampering detection and, by default, wait |
Analyze text truthscan_analyze_text | Submit a text value or public web URL for AI-written-text detection |
Analyze video truthscan_analyze_video | Analyze exactly one public video URL or uploaded video for AI generation or face swapping |
Try it: find the TruthScan tool you need
Browse the 8 TruthScan tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use TruthScan to check credits and walk me through the result in plain English.
Use TruthScan to download image asset and walk me through the result in plain English.
Pull the relevant data from TruthScan, summarize it in plain English, and point out anything that needs attention.
Use TruthScan to analyze audio and walk me through the result in plain English.
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 TruthScan working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the TruthScan API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected TruthScan 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 TruthScan. | 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 TruthScan actions to the runtime in a format your agent can reliably use. | 8 tools for TruthScan are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes TruthScan 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 TruthScan in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the TruthScan 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 TruthScan skill but can't call the tools
The ClawHub skill teaches OpenClaw about TruthScan, but the calls run through the ClawLink plugin and your connected account. Make sure TruthScan 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 TruthScan 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 TruthScan tools
TruthScan 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 TruthScan 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.
TruthScan 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 TruthScan 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 TruthScan integration?
Yes. ClawLink is the fastest way to connect OpenClaw to TruthScan: link your TruthScan account once in the browser and OpenClaw can call the TruthScan API through 8 ready-made tools — no custom code or token handling.
How do I add TruthScan to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink TruthScan skill from ClawHub, then you click Connect in the dashboard to authorize TruthScan. OpenClaw calls the tools from the next message — no config files, and the TruthScan key you paste is stored server-side instead of in your environment.
How long does it take to connect TruthScan to OpenClaw?
About two minutes. Sign in, click Connect next to TruthScan in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring TruthScan 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 TruthScan working from chat.
OpenClaw installed the TruthScan skill but can't call the tools
The ClawHub skill teaches OpenClaw about TruthScan, but the calls run through the ClawLink plugin and your connected account. Make sure TruthScan 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 DataRobot integration
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
OpenClaw Chatbotkit integration
ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
Just One API tools
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.