How to connect BuiltWith to Hermes Agent
Connect BuiltWith to Hermes with ClawLink: paste your BuiltWith key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.
BuiltWithAPI KEYMCPBuiltWith is a web technology profiler that provides insights into the technologies used by websites, including analytics, hosting, and content management systems.. Once connected, Hermes Agent can read and act on BuiltWith from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent BuiltWith access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical BuiltWith setup: pair once in the browser and your always-on Hermes agent can act on BuiltWith for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect Hermes to BuiltWith.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect BuiltWith
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with BuiltWith?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect BuiltWith in the ClawLink dashboard — paste your BuiltWith API key once.
Verify the connection by asking Hermes:
Create it in BuiltWith for me, then confirm the important fields before you finish.
Using a different agent?
The Hermes 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 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.
BuiltWith MCP for Hermes
Looking for a BuiltWith MCP server for Hermes Agent? ClawLink connects BuiltWith to Hermes Agent and exposes 10 BuiltWith tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw BuiltWith integration works the same way.
What the Hermes Agent BuiltWith integration can do
10 BuiltWith tools are ready for Hermes Agent once the account is connected.
All 10 BuiltWith tools for Hermes
| 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 |
Try it: find the BuiltWith tool you need
Browse the 10 BuiltWith tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Create it in BuiltWith for me, then confirm the important fields before you finish.
Use BuiltWith to datasets lookup and walk me through the result in plain English.
Use BuiltWith to domain api lookup and walk me through the result in plain English.
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 Hermes Agent. 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 Hermes Agent 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 comparison.
Troubleshooting
Hermes paired but still can't use BuiltWith
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
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.
FAQ
Is there a Hermes Agent BuiltWith integration?
Yes. ClawLink is the fastest way to connect Hermes to BuiltWith: link your BuiltWith account once in the browser and Hermes Agent can call the BuiltWith API through 10 ready-made tools — no custom code or token handling.
How do I connect BuiltWith to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect BuiltWith in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to BuiltWith in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want BuiltWith working from chat.
Hermes paired but still can't use BuiltWith
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
