builtwith-api

TypeScript/CLI wrapper for the BuiltWith API to look up technologies for domains/companies, retrieve lists and relationships, and support multiple response formats (JSON/XML/CSV/TSV/TXT). Includes an MCP server (separate package) exposing the same 13 methods as MCP tools.

Evaluated Mar 30, 2026 (0d ago)
Homepage ↗ Repo ↗ Ai Ml ai-ml api mcp cli technology-detection typescript zod web-intelligence web-scraping devtools
⚙ Agent Friendliness
61
/ 100
Can an agent use this?
🔒 Security
59
/ 100
Is it safe for agents?
⚡ Reliability
29
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
75
Error Messages
0
Auth Simplicity
95
Rate Limits
20

🔒 Security

TLS Enforcement
90
Auth Strength
65
Scope Granularity
25
Dep. Hygiene
40
Secret Handling
70

Uses API key authentication (no OAuth/scopes described). README provides guidance to pass keys via env var/CLI flags but does not describe logging redaction, secret storage, or rate-limit/error semantics. HTTPS/TLS is implied by API usage via native fetch and typical web conventions, but explicit enforcement is not stated in the provided text.

⚡ Reliability

Uptime/SLA
0
Version Stability
55
Breaking Changes
30
Error Recovery
30
AF Security Reliability

Best When

You want an agent/CLI-friendly way to query web technology intelligence from Node.js (>=18) using a single API key, including MCP tool integration.

Avoid When

You require built-in free tier clarity, explicit rate-limit/retry semantics, or very strict security posture around secret handling and data residency guarantees not stated in docs.

Use Cases

  • Domain technology intelligence and lookup
  • Finding sites using a given technology (with pagination)
  • Identifying related domains and keywords
  • Assessing technology adoption trends over time
  • Brand/company-to-website discovery
  • Live technology detection and trust/fraud signal checks
  • E-commerce product search

Not For

  • Use as a replacement for authoritative or legal-grade fraud/compliance determinations
  • Scenarios requiring fine-grained per-user authorization or OAuth delegation (API key only)
  • Applications needing an SDK with long-lived backward compatibility guarantees (noted breaking changes in v3)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
Yes
Webhooks
No

Authentication

Methods: API key via BUILTWITH_API_KEY env var API key via CLI flag --api-key
OAuth: No Scopes: No

No OAuth described; auth appears to be a single API key used across library, CLI, and MCP server.

Pricing

Free tier: No
Requires CC: No

Pricing and free-tier details are not provided in the provided README content.

Agent Metadata

Pagination
offset-based via NextOffset (offset: 'o...')
Idempotent
True
Retry Guidance
Not documented

Known Gotchas

  • TXT response format is noted as only for lists API
  • Pagination requires using the exact NextOffset value; 'END' indicates no more pages
  • v3 is ESM-only with named exports; agents/scripts using require() or default import may break

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for builtwith-api.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

6533
Packages Evaluated
19870
Need Evaluation
586
Need Re-evaluation
Community Powered