# How to connect BigDataCloud to OpenClaw (paste one key, 17 tools) > Connect BigDataCloud to OpenClaw with ClawLink: paste your BigDataCloud key once and 17 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/big-data-cloud The usual route to BigDataCloud 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 BigDataCloud setup: install one ClawHub skill, connect BigDataCloud in the browser, and OpenClaw can call real BigDataCloud 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 BigDataCloud. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect BigDataCloud** — 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 big-data-cloud # connect BigDataCloud (browser OAuth) npx -y @useclawlink/cli actions big-data-cloud # list available actions npx -y @useclawlink/cli run big-data-cloud --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 BigDataCloud in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your BigDataCloud API key once. Verify the connection by asking OpenClaw: > Use BigDataCloud to am i roaming api 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 BigDataCloud is connected in the dashboard, that agent calls the same 17 BigDataCloud 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). ## BigDataCloud MCP for OpenClaw Looking for a BigDataCloud MCP server for OpenClaw? ClawLink connects BigDataCloud to OpenClaw and exposes 17 BigDataCloud 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 BigDataCloud integration](https://claw-link.dev/hermes/big-data-cloud) works the same way. ## What the OpenClaw BigDataCloud integration can do 17 BigDataCloud tools are ready for OpenClaw once the account is connected. ### All 17 BigDataCloud tools for OpenClaw | Tool | What it does | |---|---| | **Am i roaming API** `big_data_cloud_am_i_roaming_api` | Determine if the user is roaming based on their IP address and GPS coordinates | | **Asn extended receiving from info API** `big_data_cloud_asn_extended_receiving_from_info_api` | Return upstream providers (receivingFrom) for a given ASN | | **Asn extended transit to info API** `big_data_cloud_asn_extended_transit_to_info_api` | Return downstream customers (transitTo) for a given ASN | | **Asn rank list API** `big_data_cloud_asn_rank_list_api` | Retrieves a ranked list of Autonomous Systems (ASNs) sorted by IPv4 address announcement volumes | | **Bgp active prefixes API** `big_data_cloud_bgp_active_prefixes_api` | Retrieve IPv4 or IPv6 prefixes currently announced on BGP | | **Country by ip address API** `big_data_cloud_country_by_ip_address_api` | Geolocate an IP address and retrieve country details and demographics | | **Country info API** `big_data_cloud_country_info_api` | Fetch detailed country information by ISO code | | **Email address verification API** `big_data_cloud_email_address_verification_api` | Verify email addresses for syntax, domain validity, and disposability | | **Hazard report API** `big_data_cloud_hazard_report_api` | Fetch a cybersecurity hazard report for a specified IP address | | **Network by cidr** `big_data_cloud_network_by_cidr` | Retrieve BGP-announced networks within a specified CIDR range | | **Network by ip address API** `big_data_cloud_network_by_ip_address_api` | Retrieve registry, ASN, and BGP details for a given IP address’s network | | **Phone number validation by ip** `big_data_cloud_phone_number_validation_by_ip` | Validate phone numbers by inferring country from client IP | | **Reverse geocoding timezone API** `big_data_cloud_reverse_geocoding_timezone_api` | Return reverse geocoding and time zone info for given coordinates | | **Time zone by ip address API** `big_data_cloud_time_zone_by_ip_address_api` | Retrieve time zone information for a given IP address | | **Tor exit nodes geolocated API** `big_data_cloud_tor_exit_nodes_geolocated_api` | Retrieve a paginated list of active TOR exit node IP addresses with geolocation and carrier | | **User agent parser API** `big_data_cloud_user_agent_parser_api` | Parse a User-Agent string into device, OS, browser, and bot details | | **User risk API** `big_data_cloud_user_risk_api` | Return a risk assessment for a user based on IP signals for fraud prevention | ## Example prompts **Am I Roaming Api** > Use BigDataCloud to am i roaming api and walk me through the result in plain English. **Asn Extended Receiving From Info Api** > Use BigDataCloud to asn extended receiving from info api and walk me through the result in plain English. **Asn Extended Transit To Info Api** > Use BigDataCloud to asn extended transit to info api and walk me through the result in plain English. **Asn Rank List Api** > Use BigDataCloud to asn rank list api 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 BigDataCloud working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the BigDataCloud API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected BigDataCloud 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 BigDataCloud. | 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 BigDataCloud actions to the runtime in a format your agent can reliably use. | 17 tools for BigDataCloud are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes BigDataCloud 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 BigDataCloud in the browser, and the 17 tools above work from chat. There is no SDK and no config file, and the BigDataCloud 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 BigDataCloud skill but can't call the tools The ClawHub skill teaches OpenClaw about BigDataCloud, but the calls run through the ClawLink plugin and your connected account. Make sure BigDataCloud 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 BigDataCloud 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 BigDataCloud tools BigDataCloud 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 BigDataCloud 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. ### BigDataCloud 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 BigDataCloud has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw BigDataCloud integration? Yes. ClawLink is the fastest way to connect OpenClaw to BigDataCloud: link your BigDataCloud account once in the browser and OpenClaw can call the BigDataCloud API through 17 ready-made tools — no custom code or token handling. ### How do I add BigDataCloud to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink BigDataCloud skill from ClawHub, then you click Connect in the dashboard to authorize BigDataCloud. OpenClaw calls the tools from the next message — no config files, and the BigDataCloud key you paste is stored server-side instead of in your environment. ### How long does it take to connect BigDataCloud to OpenClaw? About two minutes. Sign in, click Connect next to BigDataCloud in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring BigDataCloud 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 BigDataCloud working from chat. ### OpenClaw installed the BigDataCloud skill but can't call the tools The ClawHub skill teaches OpenClaw about BigDataCloud, but the calls run through the ClawLink plugin and your connected account. Make sure BigDataCloud 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 tools](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](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.