kadi_bence/tech-stack-detector
kadi_bence--tech-stack-detectorThis tool calls the Actor "kadi_bence/tech-stack-detector" and retrieves its output results. Actor description: $1.50 per 1,000 websites. Detect the technology stack of websites (Wappalyzer/BuiltWith alternative). Input: URLs or domains; optional category filter. Returns per site: CMS, ecommerce, analytics, frameworks, CDN, server and payment processors with versions and confidence, from 7,600+ fingerprints.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "kadi_bence--tech-stack-detector"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| urls | No | Websites to analyse: a JSON list like ["example.com", "https://example.com/shop"], or one string ("example.com", or several separated by commas or new lines). https:// is added when missing (with fallbacks to www. and http://). Duplicates are skipped. Max 100,000 per run. Also accepted under the aliases url, startUrls (strings or {"url": ...} objects), domains, domain, websites, website. Example values: ["https://apify.com","wordpress.org","www.allbirds.com","vercel.com","www.bbc.com"] | |
| waitSecs | No | Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget. | |
| minConfidence | No | Hide technologies detected with a lower confidence score. Most detections are 100; weaker signals (e.g. a generic script name) score 25-75. Example: 75 for a stricter list. | |
| maxConcurrency | No | How many websites are analysed at the same time. Each website is still fetched politely (robots.txt, crawl-delay). Example: 20-50 for large lists. Example values: 10 | |
| onlyCategories | No | Return only technologies in these categories, e.g. CMS, Ecommerce, Analytics. Leave empty for all 100+ categories. Sites with nothing found in your categories are not charged. | |
| includeEvidence | No | Add up to 5 "evidence" strings per technology showing what matched (header, script URL, meta tag, cookie...), e.g. scriptSrc: https://cdn.shopify.com/... Useful to audit detections; makes the dataset bigger. | |
| includeVersions | No | Add the version number when the site exposes it (e.g. WordPress 7.2, jQuery 3.6.0). Example values: true | |
| maxPagesPerSite | No | 1 = only the URL you give (usually the homepage), fastest. 2-10 = also analyse a few same-site pages linked from it (pricing, shop, blog...), which finds tools that are loaded only on inner pages. You still pay once per website. Example: 3 Example values: 1 | |
| proxyConfiguration | No | Usually not needed. If some sites answer 403 "blocked", you can try Apify Proxy (datacenter). Residential proxies are not supported. Example values: {"useApifyProxy":false} | |
| requestTimeoutSecs | No | Give up on a slow website after this many seconds (one retry on 429/5xx answers). Pages are read up to 3 MB. Example values: 20 |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key | |
| runId | Yes | Actor run ID | |
| stats | No | Run statistics | |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED | |
| actorId | Yes | Stable Apify Actor ID from the run record | |
| summary | Yes | Past-tense summary of the run state | |
| exitCode | No | Actor process exit code; populated for terminal states (especially FAILED) | |
| nextStep | Yes | One primary follow-up action with identifiers interpolated | |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry. | |
| actorName | No | "username/actor-name" | |
| startedAt | No | ISO timestamp when the run started | |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) | |
| statusMessage | No | Pass-through from Apify run.statusMessage | |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only for Console sessions |