Responsive Visual QA Matrix
Pricing
from $33.50 / 1,000 responsive visual qa matrix verdicts
Responsive Visual QA Matrix
Runs a headless-Chromium responsive QA pass on each URL across desktop/tablet/mobile and returns one verdict per URL: per-viewport layout metrics, a horizontal-overflow flag per viewport, missing-resource evidence, and a cross-viewport perceptual diff. Billed once per completed matrix.
Pricing
from $33.50 / 1,000 responsive visual qa matrix verdicts
Rating
0.0
(0)
Developer
NexGen Watch
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
10 hours ago
Last modified
Categories
Share
Runs a headless-Chromium responsive QA pass on each URL across a desktop/tablet/mobile matrix and returns ONE verdict per URL: per-viewport layout metrics, a horizontal-overflow flag per viewport, missing-resource evidence, and a cross-viewport perceptual diff. Billed once per completed matrix — never per screenshot.
What you submit
urls — page urls. Page URLs to QA across a viewport matrix. Per URL ONE record covering three bounded captures (desktop 1280x800, tablet 768x1024, mobile 390x844): per-viewport layout metrics, a horizontal-overflow flag per viewport, missing-resource evidence, and a cross-viewport perceptual diff. Billed once per completed matrix (never per screenshot). A URL blocked (robots/SSRF/403/429/5xx) or unreachable is an unbilled status, never a broken-site verdict.
The runtime source gate (per submitted target)
You choose the targets, so the source contract is enforced at run time — for every submitted URL — per origin, before any page is read:
- robots.txt fetched once per origin and honored; no robots / 404 = permitted, a disallowed path or an unavailable/forbidden robots file = BLOCKED.
- SSRF guard — every host is resolved and must be public; private, loopback, link-local, reserved and cloud-metadata addresses are refused before a socket opens.
- HTTP —
403/429/5xx= BLOCKED; DNS / timeout / connection faults = UNREACHABLE.
A BLOCKED or UNREACHABLE target is delivered as an unbilled status row — never a broken-site verdict, and never charged.
Output & billing
One row per URL. A completed matrix (all three viewports captured) carries outcome: answer and bills once — never once per screenshot. A URL blocked (robots / SSRF / 403 / 429 / 5xx) or unreachable is delivered as an unbilled status row, never a broken-site verdict. Push-then-charge: every row is delivered before its charge, so a billing hiccup can only ever undercharge.
Pricing
| Event | Price | When |
|---|---|---|
apify-actor-start | $0.02 | once when the run starts (reserved; never charged in code) |
responsive_page_check | $0.05 | once per completed desktop/tablet/mobile matrix (blocked / unreachable / unparseable never bill) |
Volume tiers reduce the per-verdict price as usage grows: $0.05 → $0.045 → $0.04 → $0.0335.
Why this and not the obvious alternative
one responsive layout verdict per URL across a desktop/tablet/mobile matrix — overflow, missing resources, and a cross-viewport perceptual diff in a single billed record — not fleet-1's interactive browser MCP and not a per-screenshot capture API.