Technology lookup API

A technology lookup API that reads what a website is built on from a single homepage fetch: CMS and e-commerce platform, JavaScript frameworks, analytics, marketing pixels, payment providers, chat widgets, email tools, anti-bot widgets, fonts, CDN and web server. Pass up to 50 domains and get one row each, priced per site — no subscription, no seat, no minimum.

By Aldo Morese, founder of QuanticData · Published Aug 21, 2026 · Updated Sep 3, 2026

Get my free API key See the request

$0.003 per delivered site · $2 free every month · Failed runs never billed

POST /v1/scraper/collectors/tech_stack/run

$ curl $QD/tech_stack/run \
    -H "Authorization: Bearer $QD_API_KEY" \
    -d '{"domains": ["nytimes.com", "allbirds.com"]}'
{ "status": "done", "count": 10,
  "results": [
    {
      "domain": "…",
      "url": "…",
      "cms": "…",
      "ecommerce_platform": "…" } ],
  "cost": 0.03 }
# 10 sites × $0.003 · nothing delivered, nothing charged

Technology lookup API: domains and country in, a residential exit in the middle, delivered rows with domain, cms and ecommerce_platform on the right, $0.003 per site. — You send domains and country; the run goes out through a residential exit and comes back as sites with domain, cms and ecommerce_platform — 18 fields on every row — and you are billed $0.003 for each site actually delivered, nothing for a run that delivers none.

$0.003 / site666 sites on the free $2 every month

Semantic inputdomains, country, max_results — no URL lists

Up to 50sites per run, pagination handled for you

No browserread over HTTP/TLS — cheaper and faster than rendering

Try it

Website tech stack, running now

Change the input and run it against the live collector — nothing to install, no sign-up.

Run it from your own code, on your own inputs

Same collector, same rows — $2 of free API credit every month, no card.

Get my free API key

What a technology lookup API does

Detection runs over four surfaces at once, because no single one is reliable on its own: the HTML itself, the URLs of the scripts and stylesheets it loads, the response headers, and the generator meta tag. Ninety-plus signatures sit on top of that, and the order inside a category is deliberate — WooCommerce is tested before WordPress, so the scalar ecommerce_platform reports the specific platform rather than the CMS underneath it. CDN and web server come from headers only (cf-ray, x-vercel-id, x-nf-request-id): guessing edge providers from markup is how detection tools end up confidently wrong.

The output is shaped for joins, not for reading. Scalars where a site can only have one answer — cms, ecommerce_platform, cdn, server — and arrays where it can have several, plus technologies with every detection as { name, category } and a tech_count for sorting. That is what makes "every Shopify store in my list that also runs Klaviyo" a predicate on your side instead of a support ticket on someone else's.

Limits, in plain numbers

Everything that bounds one run of this collector. No hidden throttles.

Max per run

50 sites

Price

$0.003 / site

Per 1,000

$3.00

Failed runs

Free zero rows, zero charge

Free every month

$2 no card

Rate limit

60 req/min on the free tier

What one site looks like

Every delivered site carries these fields. Nullable means the source did not publish it — the field stays empty instead of being guessed.

Field	Type	What it holds
`domain`	string	Registrable host (no www).
`url`	string	Final homepage URL fetched.
`cms`	string · nullable	Content management system / site builder.
`ecommerce_platform`	string · nullable	E-commerce platform.
`frameworks`	string[]	JS frameworks and libraries.
`analytics`	string[]	Analytics and product-analytics tools.
`marketing`	string[]	Ad and marketing pixels.
`payments`	string[]	Payment providers loaded on the page.
`chat`	string[]	Chat / support widgets.
`email_marketing`	string[]	Email marketing / CRM scripts.
`security`	string[]	CAPTCHA / anti-bot widgets.
`fonts`	string[]	Font services.
`other`	string[]	Other detected SaaS (CDN media, search, error tracking, consent).
`cdn`	string · nullable	CDN / edge platform from response headers.
`server`	string · nullable	Web server from the Server header.
`generator`	string · nullable	Raw content of the generator meta tag.
`technologies`	object[]	Every detection as { name, category }.
`tech_count`	integer	Total technologies detected.

Inputs

The whole request. Anything you leave out falls back to the default shown in the catalog.

Input	Type	Required	What it does
`domains`	array	yes	Domains or site URLs, one per line (max 50).
`country`	string	no	ISO 3166-1 alpha-2 code — proxy exit geo and Google locale (gl). Omit for the default pool.
`max_results`	integer	no	How many sites to deliver at most (1–50). You pay only for delivered sites.

Pricing

Technology lookup API pricing

$0.003 per delivered site. A run that delivers nothing costs nothing: blocked pages, challenges and retries are on us, and the $2 monthly allowance covers about 666 sites before you spend anything.

$0.003per delivered site$3 per 1,000 delivered sites

666 siteson the free allowance$2 every month, no card

Zero rowszero chargeblocks, captchas and retries are on us

−30%on volume tiersthe catalog returns your key's price

Pay as you go

$0/mo

$2 free credit / month
60 requests / min
List unit prices

Starter

$19/mo

$15 free credit / month
300 requests / min
10% off unit prices

Growth

$79/mo

$50 free credit / month
600 requests / min
20% off unit prices

Scale

$299/mo

$250 free credit / month
1,200 requests / min
30% off unit prices

Same wallet, same key and same $2 monthly allowance as every other Data API. Prices are launch pricing read live from the billing config — GET /v1/scraper/collectors returns the price your key actually pays.

Integration

One POST, typed rows

Base URL https://api.quanticdata.io/v1, Bearer auth, the same key as every other Data API. Endpoint: POST /v1/scraper/collectors/tech_stack/run.

curl -X POST https://api.quanticdata.io/v1/scraper/collectors/tech_stack/run \
  -H "Authorization: Bearer $QD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domains":["nytimes.com","allbirds.com"]}'

import requests

r = requests.post(
    "https://api.quanticdata.io/v1/scraper/collectors/tech_stack/run",
    headers={"Authorization": f"Bearer {QD_API_KEY}"},
    json={
        "domains": [
            "nytimes.com",
            "allbirds.com"
        ]
    },
    timeout=120,
)
for row in r.json()["payload"]["results"]:
    print(row)

const res = await fetch(
  "https://api.quanticdata.io/v1/scraper/collectors/tech_stack/run",
  {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.QD_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({"domains":["nytimes.com","allbirds.com"]}),
  },
);
const { payload } = await res.json();
console.table(payload.results);

claude mcp add quanticdata \
  -e QUANTICDATA_API_KEY=qd_live_your_key_here \
  -- npx -y quanticdata-mcp

# then, in the chat:
> run the tech_stack collector with domains=["nytimes.com","allbirds.com"]

What people build with the technology lookup API

Three shapes of work this endpoint was designed around.

Lead segmentation

Push your prospect list through it and filter by platform: every Shopify store, every site on Magento about to migrate, every account already paying for a competitor's widget. The segment is a WHERE clause, and it costs a third of a cent per domain.

Competitor and market research

Profile a whole category at once and count platforms, pixels and payment providers across it — the same market-share picture the subscription tools sell, computed from your own list.

Stack change monitoring

Re-run monthly and diff technologies: a CMS replatform, a new analytics vendor or a dropped chat widget are all buying signals, and they show up as a changed row.

Technology lookup API versus rolling your own

The differences that actually cost time when you build this in-house.

	DIY scraper	This collector
Pricing	A subscription from $295/month before the first lookup	$0.003 per site delivered, nothing else
Detection surfaces	Markup patterns only	HTML, script URLs, response headers and generator meta
CDN and server	Inferred from the page, often wrong	Read from response headers, or left null

What people search for

Live autocomplete demand around Website tech stack, pulled with our own Keyword ideas collector.

Technology lookup API: the POST to /v1/scraper/collectors/tech_stack/run with domains and country on the left, and the JSON envelope on the right with 20 sites and usage.cost_usd $0.06. — The same call you would paste into a terminal: a Bearer key, domains and country in the body, and back the envelope every QuanticData endpoint returns — type, message, payload — where count is how many sites arrived and usage.cost_usd is $0.06, which is 20 × $0.003. A run that delivers nothing costs nothing. The key is good for 60 req/min on the free tier.

Sources and standards

The platform documentation and standards this collector is built against — check any claim on this page against the primary source:

FAQ

Questions we get about the technology lookup API.

Something else? Ask us →

How many technologies can it detect?

Over ninety signatures across CMS and e-commerce, JS frameworks, analytics, marketing pixels, payments, chat, email marketing, security widgets, fonts, CDN and web server. Everything detected lands in technologies as a name plus a category, and the category arrays are views over the same detections.

Does it crawl the whole site?

No — one fetch of the homepage per domain, which is where the platform, the tag manager and the pixels live. That is what keeps it fast enough to run 50 domains in a single call and cheap enough to price per site.

Why is a technology I know is there missing?

Because it was not on the homepage or not visible without JavaScript. A tool loaded only on the checkout, or injected by a tag manager after render, leaves no signature on the page we read. A missing value is reported as missing rather than guessed — cms: null means "no signature", not "no CMS".

Can I use it on a list of leads?

That is the main use: pass up to 50 domains per run in domains, one row comes back per site, and you pay only for the rows delivered. Domains that do not answer are reported as failed and never billed.

Is there a free technology lookup API?

Every account gets $2 of credit every month with no card, which is about 666 delivered sites on this endpoint at $0.003 each. It renews monthly, and a run that delivers nothing is never billed — so a failed or blocked attempt does not eat the allowance.

How much does one run cost?

Multiply the rows you actually receive by $0.003. A run capped at 50 sites — the maximum for this collector — costs $0.15 if every row comes back, and less when the source has fewer. Volume tiers take up to 30% off, and GET /v1/scraper/collectors returns the price your key actually pays.

Run the technology lookup API now

$2 of free credit every month, no card. Your key returns its own prices from GET /v1/scraper/collectors.

Get my free API key