A Wappalyzer API alternative that shows the evidence for each technology

What to compare in a tech stack API, what Wappalyzer and BuiltWith offer developers, and how ours answers: each technology with the line it was found in, free monthly credits and an MCP server.

Wappalyzer is the best-known way to see what a website runs on, and its API is what many developers reach for first. Then they find that the API comes with a paid plan, or that an answer names a technology without saying why. If you’re looking for another option, here is what to compare, what Wappalyzer and BuiltWith offer today, and how the CheckAnySite API answers the same question.

The short version: our API returns each technology a site shows with the exact line, header or address it was found in, plus the site’s AI builder traces, popularity and domain history if you ask. A free key comes with monthly credits, and a stored tech stack costs the least of any check. If you need lead lists, company and contact data or CRM integrations, Wappalyzer and BuiltWith are built for that and we aren’t.

What Wappalyzer’s API offers

As listed on Wappalyzer’s pricing page and lookup API docs on 14 November 2026:

  • A Business plan is needed for the technology lookup API. Business is $450 a month (17% less billed yearly) and includes 20,000 API credits. Credits included in a plan expire after 60 days.
  • A lookup costs 1 credit per URL, or 5 when it crawls several pages live. Up to 10 URLs go in one request.
  • Free accounts get 50 technology lookups a month in Wappalyzer’s own app, not through the API.
  • Each technology comes with its name, categories, versions when known, a traffic rank and when it was last confirmed. Extra field sets add company details, email addresses, phone numbers and social profiles.
  • A hosted MCP server lets AI clients run lookups. It also needs the Business plan.

What the documented response doesn’t include is the reason for each technology: the part of the page that matched.

What BuiltWith offers

BuiltWith’s free API gives, for a website, how many technologies it uses in each group and category and when they were last updated, at one request a second. Its other endpoints and its MCP server spend paid API credits; its llms.txt also lets an agent pay as it goes, 10 lookups for $0.50 (both as listed on 14 November 2026). Like Wappalyzer, BuiltWith is built around lead generation: lists of the sites that use a technology, with company and contact data.

What to compare

  1. What it costs to start. Can you try the API on real sites before paying, and do unused credits carry over?
  2. Whether an answer shows why. A technology without evidence is hard to check, and a false positive ends up in your data unnoticed.
  3. Stored or live. A stored result answers fast and cheaply; a live scan answers for sites nobody looked at yet. You want both, and the date each answer was read.
  4. Coverage. Which technologies matter for your use: shop systems, frameworks, analytics, hosting, site builders.
  5. Agents. Whether Claude, ChatGPT or Cursor can ask it directly, through an MCP server.
  6. What else comes with it. Contact data for sales, or facts about the site itself: its popularity, its domain’s age, its trust signals.

How CheckAnySite answers

Ask for a site’s stored result with the tech check:

curl "https://api.checkanysite.com/v1/sites/stripe.com?checks=tech" \
  -H "Authorization: Bearer $CHECKANYSITE_API_KEY"

What comes back:

  • tech.technologies: each technology with its name, its category (such as framework, cms, analytics or hosting) and its evidence: where we saw it (“index.html, line 14”, “response header”), the snippet as it appears, and the match that gave it away.
  • tech.network: the network that announces the site’s address.
  • scannedAt: when we read the site, and resultUrl: our result page, where a person sees the same evidence.

A lookup reads the stored result and never scans. For a site we haven’t seen, POST /v1/scans scans it now; the quickstart shows both, and POST /v1/sites/batch looks up 50 sites in one request.

Add checks to the same call: ai for AI website builder traces (Lovable, Bolt, v0 and others), popularity for public ranked lists, history for when the domain was registered, trust for signals such as contact details and HTTPS. Each check has its own price, and a call never costs more than every check at once.

Ask your AI agent

The same answer is the get_tech_stack tool in our MCP server. In Claude Code:

claude mcp add --transport http checkanysite https://checkanysite.com/mcp \
  --header "Authorization: Bearer $CHECKANYSITE_API_KEY"

Then ask in plain words: “What does stripe.com run on? Show the evidence.” In the Claude app, connect CheckAnySite from the Connectors Directory and sign in, with no key to copy. The MCP docs cover every client.

Where each one fits

  • Choose Wappalyzer or BuiltWith for lead lists by technology, company and contact data, CRM integrations, a wider catalogue of technologies, or past results month by month.
  • Choose CheckAnySite to check sites you already have, from code or an agent, when each answer must show its evidence, or when you also want AI builder traces, AI readiness, popularity and domain history in the same call.

We recognise more than 600 technologies and 70 site builders (November 2026); our signature list changes in the open, and What is this website built with? explains how technologies give themselves away.

What it costs

A free key comes with monthly credits, free while the API launches. Each check costs credits, fewer from a stored result than with a new scan. Get a key, where every check, its price and its MCP tool are listed.

Real websites made with AI builders

Put it to work

Something here out of date or wrong? Tell us and we’ll fix it, with the date of the change.