Tech Stack

Detects the technologies behind a domain. It fetches the homepage live and matches fingerprints in the HTML and response headers, and in parallel looks up link graph data to catch technologies the homepage does not show directly. Use it for lead enrichment, competitor research or platform targeting.

Request

Parameters

Example

curl "https://api.rankparse.com/v1/tech-stack?domain=vercel.com" \
  -H "X-API-Key: rp_your_key"

import requests

resp = requests.get(
    "https://api.rankparse.com/v1/tech-stack",
    params={"domain": "vercel.com"},
    headers={"X-API-Key": "rp_your_key"},
    timeout=45,
)
resp.raise_for_status()
for tech in resp.json()["data"]["technologies"]:
    print(tech["category"], tech["name"], tech["confidence"])

const res = await fetch(
  "https://api.rankparse.com/v1/tech-stack?domain=vercel.com",
  { headers: { "X-API-Key": process.env.RANKPARSE_API_KEY } }
);
if (!res.ok) throw new Error(`${res.status}: ${await res.text()}`);
const { data } = await res.json();
for (const t of data.technologies) console.log(t.category, t.name, t.confidence);

Response

{
  "domain": "vercel.com",
  "data": {
    "domain": "vercel.com",
    "technologies": [
      { "name": "Next.js", "category": "framework", "confidence": "definite" },
      { "name": "React", "category": "framework", "confidence": "high" },
      { "name": "Cloudflare", "category": "cdn", "confidence": "definite" },
      { "name": "Vercel", "category": "hosting", "confidence": "definite" },
      { "name": "Google Analytics 4", "category": "analytics", "confidence": "definite" }
    ],
    "server": "cloudflare",
    "x_powered_by": null,
    "response_time_ms": 241
  },
  "credits_used": 2,
  "credits_remaining": 998
}

Response fields

Categories

Confidence levels

• definite: a unique identifier in the headers or HTML (for example the cf-ray header means Cloudflare).
• high: a strong pattern match (for example __NEXT_DATA__ in the HTML means Next.js).
• medium: a weaker signal that can produce false positives.

Behavior and limits

• Two sources, merged by name. The live homepage fetch takes precedence. Technologies that the link graph lookup finds but the live page does not show (for example a script or CDN host the site links to) are added. The response does not mark which source produced each entry.
• Lookup budget. The link graph lookup is cut off after 12 seconds; if it is slow, you get the live result alone rather than waiting.
• Homepage only. Live detection reads the homepage's HTML and headers. Technologies loaded only after JavaScript runs may be missed, and inner pages are not inspected.
• Fetch limits. 8 second timeout for the homepage, 2 MB body cap, up to 5 redirects, public hosts only. See Page SEO for the fetch rules.
• Billing. Costs 2 credits; refunded automatically on any non-2xx response. Invalid or private domains are rejected before billing. Subject to the standard 60 requests per minute limit.

Errors

See Errors for the shared error format.

Related

MCP tool: get_tech_stack.