# How to connect BuiltWith to OpenClaw (paste one key, 10 tools) > Connect BuiltWith to OpenClaw with ClawLink: paste your BuiltWith 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/builtwith The usual route to BuiltWith 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 BuiltWith setup: install one ClawHub skill, connect BuiltWith in the browser, and OpenClaw can call real BuiltWith 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 BuiltWith. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect BuiltWith** — 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 builtwith # connect BuiltWith (browser OAuth) npx -y @useclawlink/cli actions builtwith # list available actions npx -y @useclawlink/cli run builtwith --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 BuiltWith in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your BuiltWith API key once. Verify the connection by asking OpenClaw: > Create it in BuiltWith for me, then confirm the important fields before you finish. ### 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 BuiltWith is connected in the dashboard, that agent calls the same 10 BuiltWith 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). ## BuiltWith MCP for OpenClaw Looking for a BuiltWith MCP server for OpenClaw? ClawLink connects BuiltWith to OpenClaw and exposes 10 BuiltWith 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 BuiltWith integration](https://claw-link.dev/hermes/builtwith) works the same way. ## What the OpenClaw BuiltWith integration can do 10 BuiltWith tools are ready for OpenClaw once the account is connected. ### All 10 BuiltWith tools for OpenClaw | Tool | What it does | |---|---| | **Create domain list file** `builtwith_create_domain_list_file` | Create a TXT or ZIP file from a list of domains | | **Datasets lookup** `builtwith_datasets_lookup` | Access mass Internet technology usage information from 2000 to today | | **Domain API lookup** `builtwith_domain_api_lookup` | Retrieve current and historical technology information of a website | | **Financial API lookup** `builtwith_financial_api_lookup` | Fetch financial data for a domain | | **Free API lookup** `builtwith_free_api_lookup` | Access last updated dates and counts for technology groups and categories for websites | | **Lists API get list** `builtwith_lists_api_get_list` | Retrieve a list of websites using a specific technology | | **Product API lookup** `builtwith_product_api_lookup` | Find websites selling specific eCommerce products | | **Recommendations API lookup** `builtwith_recommendations_api_lookup` | Generate a list of websites with similar technology profiles | | **Redirects API lookup** `builtwith_redirects_api_lookup` | Retrieve live and historical redirects for a website | | **Social API lookup** `builtwith_social_api_lookup` | Retrieve domains associated with social media profile URLs | ## Example prompts **Create Domain List File** > Create it in BuiltWith for me, then confirm the important fields before you finish. **Datasets Lookup** > Use BuiltWith to datasets lookup and walk me through the result in plain English. **Domain Api Lookup** > Use BuiltWith to domain api lookup and walk me through the result in plain English. **Financial Api Lookup** > Use BuiltWith to financial api lookup 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 BuiltWith working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the BuiltWith API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected BuiltWith 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 BuiltWith. | 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 BuiltWith actions to the runtime in a format your agent can reliably use. | 10 tools for BuiltWith are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes BuiltWith 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 BuiltWith in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the BuiltWith 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 BuiltWith skill but can't call the tools The ClawHub skill teaches OpenClaw about BuiltWith, but the calls run through the ClawLink plugin and your connected account. Make sure BuiltWith 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 BuiltWith 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 BuiltWith tools BuiltWith 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 BuiltWith 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. ### BuiltWith 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 BuiltWith has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw BuiltWith integration? Yes. ClawLink is the fastest way to connect OpenClaw to BuiltWith: link your BuiltWith account once in the browser and OpenClaw can call the BuiltWith API through 10 ready-made tools — no custom code or token handling. ### How do I add BuiltWith to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink BuiltWith skill from ClawHub, then you click Connect in the dashboard to authorize BuiltWith. OpenClaw calls the tools from the next message — no config files, and the BuiltWith key you paste is stored server-side instead of in your environment. ### How long does it take to connect BuiltWith to OpenClaw? About two minutes. Sign in, click Connect next to BuiltWith in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring BuiltWith 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 BuiltWith working from chat. ### OpenClaw installed the BuiltWith skill but can't call the tools The ClawHub skill teaches OpenClaw about BuiltWith, but the calls run through the ClawLink plugin and your connected account. Make sure BuiltWith 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 - [PostHog](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [DataforSEO](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase tools](https://claw-link.dev/openclaw/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.