Eimantas V

The usual failure mode of a scraper is silent. A site ships a redesign, the selectors stop matching, and the feed keeps running while returning less and less of what you asked for.

So wherever a target publishes a real API, that's what I build on. The Meta Ads Library Scraper runs on Meta's own Ad Library API. The hiring Actors read Greenhouse, Lever, Ashby, SmartRecruiters, Workable, Recruitee and Personio directly. Those endpoints don't change when someone moves a button.

Plenty of targets publish nothing. Those Actors parse pages, which means they need maintenance - I'd rather say so here than let you find out later.

Every Actor is pay-per-event: charged per result, not per compute minute, so you can work out what a job costs before you start it instead of discovering it afterwards. Most charge only for rows you actually receive, and the rule is written into the event descriptions on each Actor's pricing tab - read it before you run anything, then check it against the run log.

Meta Ads Library Scraper  is the busiest one here: ad copy, headlines, CTAs, platforms and start dates, so you can see which creatives a competitor has kept running.

Everything else is below - ads and brand, hiring signals, social and creators, e-commerce and app stores, property, SEO and monitoring. Sourcing several feeds from one account means one billing line and one person to email when something looks wrong.

Need a feed that isn't here, or one of these adapted to your shape of data? Email vesialkaeimantas@gmail.com. If an Actor misbehaves, open an issue on its page - that reaches me directly and it's the fastest way to get it fixed.