# How to connect FraudLabs Pro to OpenClaw (paste one key, 8 tools) > Connect FraudLabs Pro to OpenClaw with ClawLink: paste your FraudLabs Pro key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/fraudlabs-pro The usual route to FraudLabs Pro 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 FraudLabs Pro setup: install one ClawHub skill, connect FraudLabs Pro in the browser, and OpenClaw can call real FraudLabs Pro 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 FraudLabs Pro. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect FraudLabs Pro** — 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 fraudlabs-pro # connect FraudLabs Pro (browser OAuth) npx -y @useclawlink/cli actions fraudlabs-pro # list available actions npx -y @useclawlink/cli run fraudlabs-pro --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 FraudLabs Pro in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your FraudLabs Pro API key once. Verify the connection by asking OpenClaw: > Use FraudLabs Pro to flp screen order 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 FraudLabs Pro is connected in the dashboard, that agent calls the same 8 FraudLabs Pro 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). ## FraudLabs Pro MCP for OpenClaw Looking for a FraudLabs Pro MCP server for OpenClaw? ClawLink connects FraudLabs Pro to OpenClaw and exposes 8 FraudLabs Pro 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 FraudLabs Pro integration](https://claw-link.dev/hermes/fraudlabs-pro) works the same way. ## What the OpenClaw FraudLabs Pro integration can do 8 FraudLabs Pro tools are ready for OpenClaw once the account is connected. ### All 8 FraudLabs Pro tools for OpenClaw | Tool | What it does | |---|---| | **Flp screen order** `fraudlabs_pro_flp_screen_order` | Screen orders for fraud | | **Get order result2** `fraudlabs_pro_get_order_result2` | Retrieve an existing transaction from FraudLabs Pro fraud detection system using the v2 API | | **Get sms verification result** `fraudlabs_pro_get_sms_verification_result` | Verify an OTP (one-time password) received via SMS | | **Webhook order status changed** `fraudlabs_pro_webhook_order_status_changed` | Send a test webhook payload to the provided callback URL for FraudLabs Pro order status change | | **Create account** `fraudlabs_pro_create_account` | Creates a new FraudLabs Pro user account under a reseller account | | **Flp feedback order** `fraudlabs_pro_flp_feedback_order` | Submit fraud screening feedback to improve FraudLabs Pro's machine learning model | | **Send sms verification** `fraudlabs_pro_send_sms_verification` | Sends an SMS message containing a one-time password (OTP) to verify a user's phone number | | **Subscribe plan** `fraudlabs_pro_subscribe_plan` | Subscribe a reseller account to a specific plan | ## Example prompts **Flp Screen Order** > Use FraudLabs Pro to flp screen order and walk me through the result in plain English. **Get Order Result2** > Pull the relevant data from FraudLabs Pro, summarize it in plain English, and point out anything that needs attention. **Get Sms Verification Result** > Pull the relevant data from FraudLabs Pro, summarize it in plain English, and point out anything that needs attention. **Webhook Order Status Changed** > Use FraudLabs Pro to webhook order status changed 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 FraudLabs Pro working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the FraudLabs Pro API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected FraudLabs Pro 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 FraudLabs Pro. | 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 FraudLabs Pro actions to the runtime in a format your agent can reliably use. | 8 tools for FraudLabs Pro are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes FraudLabs Pro 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 FraudLabs Pro in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the FraudLabs Pro 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 FraudLabs Pro skill but can't call the tools The ClawHub skill teaches OpenClaw about FraudLabs Pro, but the calls run through the ClawLink plugin and your connected account. Make sure FraudLabs Pro 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 FraudLabs Pro 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 FraudLabs Pro tools FraudLabs Pro 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 FraudLabs Pro 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. ### FraudLabs Pro 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 FraudLabs Pro has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw FraudLabs Pro integration? Yes. ClawLink is the fastest way to connect OpenClaw to FraudLabs Pro: link your FraudLabs Pro account once in the browser and OpenClaw can call the FraudLabs Pro API through 8 ready-made tools — no custom code or token handling. ### How do I add FraudLabs Pro to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink FraudLabs Pro skill from ClawHub, then you click Connect in the dashboard to authorize FraudLabs Pro. OpenClaw calls the tools from the next message — no config files, and the FraudLabs Pro key you paste is stored server-side instead of in your environment. ### How long does it take to connect FraudLabs Pro to OpenClaw? About two minutes. Sign in, click Connect next to FraudLabs Pro in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring FraudLabs Pro 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 FraudLabs Pro working from chat. ### OpenClaw installed the FraudLabs Pro skill but can't call the tools The ClawHub skill teaches OpenClaw about FraudLabs Pro, but the calls run through the ClawLink plugin and your connected account. Make sure FraudLabs Pro 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 - [GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/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.