HTML to PDF Evidence Renderer
Pricing
from $33.50 / 1,000 html to pdf evidence renderer verdicts
HTML to PDF Evidence Renderer
Renders each HTML document or permitted public URL to a hashed, print-pinned PDF evidence artifact: page count, resource-failure ledger, input+output SHA-256, final URL, and an honest COMPLETE / PARTIAL label. Deterministic settings, no login or cookies.
Pricing
from $33.50 / 1,000 html to pdf evidence renderer 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
Renders each HTML document or permitted public URL to a hashed, print-pinned PDF evidence artifact: page count, resource-failure ledger, input+output SHA-256, final URL, and an honest COMPLETE / PARTIAL usability label. Deterministic settings, no login or cookies.
What you submit
sources — html strings or permitted public urls. Each item is either an inline HTML document (recognized by a leading '<' or a data:text/html URL) or a permitted public http(s) URL. URL items pass the per-origin runtime gate (robots + SSRF) before any fetch. Per item ONE hashed PDF artifact (stored in the run key-value store) with pinned print settings, page count, resource-failure list, input+output SHA-256, final URL, and an honest COMPLETE / PARTIAL label. Deterministic fonts, bounded resources, no login/cookies. A PARTIAL render bills ONLY when the artifact is a valid, openable PDF of at least one page; a render that fails to produce a usable PDF, or a blocked/unreachable URL, never bills.
The runtime source gate (per submitted target)
You choose the targets, so the source contract is enforced at run time — for every URL-mode item (inline HTML is rendered locally and is not fetched) — 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 item. A render bills once if and only if it produced a valid, openable PDF of at least one page. COMPLETE = valid PDF with zero resource failures; PARTIAL = valid, openable, paginated PDF that had one or more resource failures (a missing image/font) — still genuinely usable, so it bills. A render that never produced an openable PDF is labelled UNUSABLE and never bills; a blocked or unreachable URL never bills. 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) |
pdf_render_check | $0.05 | once per usable PDF artifact — COMPLETE or PARTIAL (UNUSABLE / blocked / unreachable 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
a hashed, print-pinned PDF evidence artifact per HTML/URL with an honest COMPLETE/PARTIAL usability label and a resource-failure ledger — not a screenshot API and not an unbounded website-to-PDF crawler.