Scrape Response Triage
Pricing
$50.00 / 1,000 completed triage reports
Scrape Response Triage
Inspect saved HTML and HTTP metadata for possible extraction failures without fetching pages.
Pricing
$50.00 / 1,000 completed triage reports
Rating
0.0
(0)
Developer
IGNITE Tools
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
21 hours ago
Last modified
Categories
Share
Check a scraper response before trusting its extracted data. A technically successful HTTP response may still contain a login form, human-verification page or JavaScript shell. This tool returns explicit review findings from saved responses.
Launch price: US$0.05 per completed report covering 1-20 responses within the limits below. One triage-completed event per report; no start fee, per-response fee or separate platform-usage charge. Malformed input fails before the report event. A completed report with findings, including a challenge warning, is still a charged report. A new run produces another report and charge. The Store Pricing tab is authoritative.
Inspect saved HTTP/HTML responses without fetching URLs, executing JavaScript or bypassing challenges. Input: responses_json JSON text array of 1-20 response objects. Required fields: unique nonblank label (128 characters), integer status_code (100-599), content_type (128 characters), html. Optional required_text and required_tags: up to 20 unique strings each, 128 characters; tags must be lowercase ASCII names. Required text uses exact case-sensitive substrings after observed whitespace collapses.
Limits: input 2 MiB UTF-8, nesting 16, 200000 JSON nodes; each HTML 256 KiB, total HTML 1 MiB, 20000 tags per response, HTML depth 128, 80 attributes per tag; report 4 MiB. Invalid, ambiguous structural input and excess limits fail without a report.
Reports flag HTTP errors, unexpected media types, possible login/challenge/shell responses and absent configured evidence. Findings are heuristic and can be wrong. no_configured_flags is not proof of correct extraction. Script/style/template/noscript/title text and comments are excluded; CSS-hidden text can still count. Malformed HTML is not repaired or rendered.
One dataset report retains labels and hashes but omits raw HTML, titles, observed text and required text. Only submit authorised non-sensitive data: input/output pass through Apify storage.
Apify SDK 4.1.0. Use 256 MiB, 60 seconds, restart-on-error off, standby off. Adapter retains an existing default-dataset report on restart; this is not an exactly-once concurrency guarantee. The implementation passed 46 shared core/boundary/adapter tests. A prior synthetic cloud run correctly separated a challenge response from a product response. These checks do not establish production reliability or customer adoption.
Quick start
Run the prefilled synthetic example in Input. It includes a challenge response and a product response; inspect responses[].findings in the one dataset report. Replace responses_json with your own authorised saved responses. A label identifies each response; raw HTML is omitted from the report.
Fits an existing pipeline
Save HTTP status, content type and HTML in your existing scraper, then supply that saved response to this Actor before downstream processing. It does not fetch a URL or connect automatically to an upstream scraper. Use the documented JSON fields through Apify API or Console.
