Gorav Agarwal

I build production web scrapers — mostly the awkward ones. Private JSON APIs behind booking engines, undocumented internal endpoints, encrypted request payloads, protobuf tokens, and anti-bot layers that reject anything that looks automated.

Most of my work has been large, long-running extraction pipelines where the target actively changes underneath you. That shapes how I build Actors here.

Actors for public data that keep working. I go after sources that take real reverse-engineering to reach cleanly, rather than crowded targets where the tenth identical scraper adds nothing.

• Reliability over feature count. An Actor thaless than one that does less and never surprisesyou.
• Honest documentation. If a field only populaADME says 65%. You should never discover a data gap in production.
• Actually maintained. Sites change — that's t rather ship a fix than let an Actor rot behind astale rating.
• No auth, no personal data. My Actors don't ad don't harvest people's contact details.

Python · Node.js · Playwright · reverse-engineereddecoding · proxy rotation · Google Apps Script

Open an issue on any of my Actors and I'll pick it ran and what you expected to get back — that'susually enough to get a fix out the same day.