# How to connect Iqair Airvisual to OpenClaw (paste one key, 10 tools) > Connect Iqair Airvisual to OpenClaw with ClawLink: paste your Iqair Airvisual key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/iqair-airvisual The usual route to Iqair Airvisual 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 Iqair Airvisual setup: install one ClawHub skill, connect Iqair Airvisual in the browser, and OpenClaw can call real Iqair Airvisual 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 Iqair Airvisual. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Iqair Airvisual** — 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 iqair-airvisual # connect Iqair Airvisual (browser OAuth) npx -y @useclawlink/cli actions iqair-airvisual # list available actions npx -y @useclawlink/cli run iqair-airvisual --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 Iqair Airvisual in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Iqair Airvisual API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Iqair Airvisual, summarize it in plain English, and point out anything that needs attention. ### 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 Iqair Airvisual is connected in the dashboard, that agent calls the same 10 Iqair Airvisual 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). ## Iqair Airvisual MCP for OpenClaw Looking for a Iqair Airvisual MCP server for OpenClaw? ClawLink connects Iqair Airvisual to OpenClaw and exposes 10 Iqair Airvisual 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 Iqair Airvisual integration](https://claw-link.dev/hermes/iqair-airvisual) works the same way. ## What the OpenClaw Iqair Airvisual integration can do 10 Iqair Airvisual tools are ready for OpenClaw once the account is connected. ### All 10 Iqair Airvisual tools for OpenClaw | Tool | What it does | |---|---| | **Get air quality forecast data** `iqair_airvisual_get_air_quality_forecast_data` | Retrieve air quality forecast data for a specified city, state, and country | | **Get cities** `iqair_airvisual_get_cities` | List supported cities in a specified state and country | | **Get city air quality** `iqair_airvisual_get_city_air_quality` | Retrieve air quality data for a specific city | | **Get countries** `iqair_airvisual_get_countries` | List all supported countries | | **Get historical aqi data** `iqair_airvisual_get_historical_aqi_data` | Retrieve historical air quality data for a city | | **Get nearest city air quality** `iqair_airvisual_get_nearest_city_air_quality` | Retrieve air quality data for the nearest city based on latitude/longitude or IP | | **Get nearest station air quality** `iqair_airvisual_get_nearest_station_air_quality` | Get nearest station air quality | | **Get states** `iqair_airvisual_get_states` | List supported states in a specified country | | **Get station by ID** `iqair_airvisual_get_station_by_id` | Fetches current air quality and weather data for a specific location by | | **Get world ranking** `iqair_airvisual_get_world_ranking` | Retrieves air quality ranking data | ## Example prompts **Get Air Quality Forecast Data** > Pull the relevant data from Iqair Airvisual, summarize it in plain English, and point out anything that needs attention. **Get Cities** > Pull the relevant data from Iqair Airvisual, summarize it in plain English, and point out anything that needs attention. **Get City Air Quality** > Pull the relevant data from Iqair Airvisual, summarize it in plain English, and point out anything that needs attention. **Get Countries** > Pull the relevant data from Iqair Airvisual, 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 Iqair Airvisual working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Iqair Airvisual API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Iqair Airvisual 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 Iqair Airvisual. | 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 Iqair Airvisual actions to the runtime in a format your agent can reliably use. | 10 tools for Iqair Airvisual are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Iqair Airvisual 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 Iqair Airvisual in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Iqair Airvisual 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 Iqair Airvisual skill but can't call the tools The ClawHub skill teaches OpenClaw about Iqair Airvisual, but the calls run through the ClawLink plugin and your connected account. Make sure Iqair Airvisual 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 Iqair Airvisual 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 Iqair Airvisual tools Iqair Airvisual 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 Iqair Airvisual 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. ### Iqair Airvisual 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 Iqair Airvisual has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Iqair Airvisual integration? Yes. ClawLink is the fastest way to connect OpenClaw to Iqair Airvisual: link your Iqair Airvisual account once in the browser and OpenClaw can call the Iqair Airvisual API through 10 ready-made tools — no custom code or token handling. ### How do I add Iqair Airvisual to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Iqair Airvisual skill from ClawHub, then you click Connect in the dashboard to authorize Iqair Airvisual. OpenClaw calls the tools from the next message — no config files, and the Iqair Airvisual key you paste is stored server-side instead of in your environment. ### How long does it take to connect Iqair Airvisual to OpenClaw? About two minutes. Sign in, click Connect next to Iqair Airvisual in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Iqair Airvisual 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 Iqair Airvisual working from chat. ### OpenClaw installed the Iqair Airvisual skill but can't call the tools The ClawHub skill teaches OpenClaw about Iqair Airvisual, but the calls run through the ClawLink plugin and your connected account. Make sure Iqair Airvisual 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](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](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.