Murat Uzun

I build small, focused Actors for people who need web data without babysitting a scraper.

What I optimise for

• Output you can actually use. Aggregated where aggregation makes sense — one row per website, not one row per page, so you import leads instead of de-duplicating fragments.
• Limits that are real. If you set "30 pages", you get 30 pages. Budget caps are enforced, not suggested, so a sprawling site can never surprise you on the bill.
• Fewer false positives. Placeholder addresses, template leftovers and image filenames get filtered out before they reach your dataset.
• Plain documentation. Every Actor's README says what it does, what it does not do, and where it will struggle.

Current tools

• Website Contact & Social Extractor — crawl any site, get one clean row per domain with e-mails, phone numbers and social profiles.

More on the way. If an Actor misbehaves or you need a field it does not return yet, open an issue on the Actor — I read them.