Public Website Tech Stack Signal Agent
Pricing
from $5.00 / 1,000 useful tech stack results
Public Website Tech Stack Signal Agent
Detect public website technology, tracking, marketing, commerce, payment, CDN, and frontend stack signals from visible HTML evidence.
Pricing
from $5.00 / 1,000 useful tech stack results
Rating
0.0
(0)
Developer
jack su
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Share
Detect public website technology and tracking-stack signals from visible HTML evidence: frontend frameworks, CMS hints, analytics, ad pixels, tag managers, marketing automation, forms, chat tools, commerce platforms, payment hints, CDN/script hosts, and source snippets.
This Actor is built for AI sales agents, market research, technographic segmentation, competitive intelligence, and website QA workflows that need a compact evidence record without running a browser or scraping private platforms.
What It Returns
- Detected technologies with category, evidence type, evidence text, evidence URL, and confidence context.
- Category summaries for analytics, ad pixels, tag managers, frontend frameworks, CMS, marketing automation, chat/support, commerce, payment, CDN, and scheduling/forms.
- Script hosts and evidence snippets that explain why each tool was detected.
- Optional focus-tool matches, diagnostics, change status, and a stable
stackHash.
Pricing Behavior
The Actor uses pay-per-event pricing and only charges the useful result event when it finds useful public technology-stack evidence.
It does not charge the useful event for:
- invalid or private-network URLs;
- failed fetches;
- pages with no technology signals;
- focus-tool misses;
- unchanged records when you pass a previous
stackHash.
apify-default-dataset-item is intentionally not used.
Safety
- Public HTTP/HTTPS pages only.
- Private-network hosts, credentials, query strings, fragments, path parameters, and token-like account paths are rejected.
- JavaScript is not executed.
- External scripts, iframes, APIs, and pixels are not fetched; only visible HTML references are recorded.
- Output is evidence-based and does not infer hidden backend systems.
Example Input
{"startUrls": ["https://www.example.com"],"focusTools": ["HubSpot","React"],"requestTimeoutSecs": 20}
Best Use Cases
- Qualify companies by public technographic evidence before sales outreach.
- Identify websites using specific marketing, analytics, commerce, or payment tools.
- Monitor stack changes without paying for unchanged results.
- Feed AI agents structured evidence instead of raw HTML.