What ViperCapture does
ViperCapture gives people and software agents one explicit render contract for public URLs, HTML, and Markdown. The hosted API can return images, video, PDF, clean HTML or Markdown, structured metadata, diagnostics, certified artifacts, slices, and responsive viewport packs. It supports Chromium, Firefox, and WebKit, along with bounded actions, assertions, readiness controls, and deterministic browser settings. The website provides a simpler capture workspace for direct, interactive use.
How the product is run
The public service is operated as a focused, security-conscious application. Browser work is isolated, private and local network destinations are blocked, custom credentials are restricted to same-origin target requests, and temporary render data has documented retention limits. ViperCapture uses Clerk for authentication, Paddle as merchant of record, Neon for application data, and UploadThing for explicitly documented temporary delivery and caching paths. Current service limits and behavior are published in the documentation rather than hidden behind sales contact.
Who it is for
ViperCapture is designed for developers, QA and documentation teams, automation workflows, and agents that need reliable evidence of how a page rendered. It is a good fit when a plain HTTP fetch cannot see the final browser state, when output must be produced in more than one browser engine, or when a caller needs structured errors and request identifiers. It is not a tool for bypassing access controls, CAPTCHAs, private networks, or a site owner’s policies.
Open source and contact
The limited self-hosted URL-to-image engine is available on GitHub under the MIT license. Hosted account, billing, credit, and extended document features are separate. Product, support, privacy, and security questions can be sent through the contact page.