BuiltWith is a web technology profiler that provides insights into the technologies used by websites, including analytics, hosting, and content management systems.
BuiltWith is a web technology profiler that provides insights into the technologies used by websites, including analytics, hosting, and content management systems. On Nagent, BuiltWith is exposed as a fully-configurable analytics integration that any agent can call — 11 actions, and API key authentication. No code is required to wire BuiltWith into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use BuiltWith to automate the kinds of tasks analytics teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire BuiltWith into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against BuiltWith, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BUILTWITH_CREATE_DOMAIN_LIST_FILETool to create a TXT or ZIP file from a list of domains. Use when preparing a domain list for bulk or firehose lookups.
Input parameters
Output file format. 'txt' for plain text, 'zip' for a ZIP archive containing the text file.
List of domain names (root domains). Duplicates will be removed automatically.
Custom output file name. Must end with .txt when format='txt' or .zip when format='zip'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUILTWITH_DATASETS_LOOKUPTool to access mass Internet technology usage information from 2000 to today. Use when you need historical technology usage trends for a domain.
Input parameters
Technology name to retrieve historical usage information for, e.g., 'Shopify', 'WordPress', 'React'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUILTWITH_DOMAIN_API_LOOKUPTool to retrieve current and historical technology information of a website. Use after confirming the domain to lookup.
Input parameters
Whether to exclude personally identifiable information from the response.
Whether to include trust and safety information.
Whether to hide download link information in the response.
Domain or URL to lookup
Whether to exclude attribution data from the response.
Whether to exclude live technology results.
Whether to exclude meta tag information from the response.
Whether to hide technology text descriptions in the response.
Whether to return only live/currently detected technologies.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUILTWITH_FINANCIAL_API_LOOKUPTool to fetch financial data for a domain. Use when you need company financials for US or UK registered websites.
Input parameters
Website domain to lookup financial information for (e.g., 'robinhood.com').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUILTWITH_FREE_API_LOOKUPTool to access last updated dates and counts for technology groups and categories for websites. Use when you need a snapshot of technology usage timing for a domain.
Input parameters
Root domain to lookup; only root domains are supported (e.g., 'builtwith.com')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUILTWITH_LISTS_API_GET_LISTTool to retrieve a list of websites using a specific technology. Use when you want to find sites leveraging a particular tech.
Input parameters
Set to 'yes' to include historical sites; cannot be used with since
Set to 'yes' to include meta data in results
Technology name (replace spaces with dashes, e.g., 'Magento')
Filter sites active since given date or relative query (e.g., '30 Days Ago'); cannot be used with all
Pagination token from previous response; 'END' means no more results
ISO 3166-1 alpha-2 country code(s) to filter results, comma-separated
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUILTWITH_MCP_API_LOOKUPDEPRECATED: Use BUILTWITH_DOMAIN_API_LOOKUP instead. Tool to query live web technologies for a root domain. Use after confirming a valid domain name.
Input parameters
Root domain to lookup (e.g., 'example.com')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUILTWITH_PRODUCT_API_LOOKUPTool to find websites selling specific eCommerce products. Use when you need to discover online retailers offering a given product name or query a domain's product listings (e.g., 'dom:jbhifi.com.au').
Input parameters
Page index for results (default 0 = first page).
Number of shops to return (default 50, max 500).
Product search string or 'dom:<domain>'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUILTWITH_RECOMMENDATIONS_API_LOOKUPTool to generate a list of websites with similar technology profiles. Use when you need technology recommendations for a given domain lookup.
Input parameters
A root domain or comma-separated list of up to 16 root domains to get technology recommendations for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUILTWITH_REDIRECTS_API_LOOKUPTool to retrieve live and historical redirects for a website. Use after confirming the exact root domain to gather inbound and outbound redirect timelines.
Input parameters
Root domain for redirects lookup; only root domains (no subdomains or paths).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUILTWITH_SOCIAL_API_LOOKUPTool to retrieve domains associated with social media profile URLs. Use when you need to map social profiles to root domains.
Input parameters
Social media profile URL or broad identifier to lookup. Supports multi-lookup of up to 16 identifiers separated by commas.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 90 agents privately built on Nagent that already use BuiltWith.
Build on Nagent
Connect BuiltWith to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find BuiltWith, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, BuiltWith is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once BuiltWith is connected, you configure its 11 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop BuiltWith steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a BuiltWith event fires, the agent kicks off automatically.
Every BuiltWith action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While BuiltWith ships with 11 pre-built analytics actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching BuiltWith together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build BuiltWith-based workflows tailored to your business.