A sellable API in three URLs

Screenshot-as-a-service is a real business several companies run. The hard part was never the screenshot; it was everything around it.

On Hoody the screenshot already exists: the browser service's /screenshot?url= returns the rendered page. Your product is an exec script in front of it: it checks the caller's key, forwards the request, and POSTs an atomic increment to a per-customer counter in SQLite. Billing reads the counters. The whole stack is three services that came with the container, arranged in a line, running on the box you already rent.

The same shape works for any Kit capability worth a price: PDF rendering, page text, thumbnails. Pick an endpoint, wrap it, meter it.

The product is a browser endpoint, a wrapper script, and a counter.