Mindcase

The maintenance tax is the part people underestimate, and the failure mode that cost us most was not scrapers breaking loudly. It was scrapers succeeding quietly. A selector drifts, the extractor returns an empty string, and the pipeline records a clean zero instead of an error. We spent weeks counting those as real results before we noticed.So the question I would put to any extraction layer: when a page changes shape and the parser finds nothing, does the API return success with an empty payload, or does it tell me it could not read the page? Those are very different products downstream.Curious how you handle that, and whether the custom APIs come with any drift detection when a source silently changes.

this is cool and you definitely hit a pain point. what do you say to a user asking what mind case can do that services like Windsor.ai cannot? im genuinely considering switching so sell me :) (for the record we mostly use gA4,GSC,google ads) as connectors and would love to have reliable(!) way to source reddit.

Thank you guys. Will give it a shot for scarping TikTok posts of my creators...

Congrats on the launch! This is a super useful tool and can save so much time for everyone, especially data scientists. Really cool that you support Instagram and TikTok, have been looking for something like this. Will give it a try and let you know what I think!

Normalizing web extraction behind a single API call shape is a total game-changer for AI teams. Super cool build, congrats!

The infrastructure piece is what makes this interesting. scraping itself is not hard until you need it to keep working.

The custom API angle is interesting. A lot of scraping tools work well for known sources, but the anything across the web problem is where teams usually get stuck.

answering Saurabh's question directly - we're a B2B SaaS and the source I'd actually pay for is G2/Capterra review pages for our competitors: review text, star rating, and reviewer company size band. Maybe 500-1000 rows a month, nothing crazy. Every competitive intel tool I've tried treats review sites as an afterthought behind the "big" platforms. Also curious about the pricing question Raunak asked above - if I fetch the same post twice in a day, am I paying twice or is there any caching on the backend?

Curious to see how this handles websites that constantly change layouts or add new restrictions. If the reliability holds up, this could become a useful foundation for many data-driven products.

This is actually pretty useful. Keeping scrapers working is such a pain, so having it all behind one API makes a lot of sense. Nice launch 👏

Reliable web data is still one of the biggest bottlenecks for AI applications. Simplifying extraction without teams having to maintain complex scraping setups feels like a valuable infrastructure layer. Great launch!

Sanjay here from the Mindcase team.A practical question for anyone evaluating a web data vendor, us included: what would you ask to figure out whether it actually works in production, not just in a demo?For me, there are three:What happens when a page only partially loads? Do I get a row with quietly empty fields, or a failure I can actually see?Am I charged for attempts, or only for rows that were successfully collected?Who notices when a site changes - you or me?Our answers are: honest errors, rows collected, and us.In my experience, when a vendor gets vague on any of those three, that’s usually where the pain starts showing up in month two.Ask us the same three questions. Hold us to the answers.

@kritishpuri Congratulations on launch, this seems like a great product replacing apify for me,but i have some questions:1. How we compare this to composio why this is better?2. If i fetch a reddit or twitter post and got charged for it today example 1$ then will i be charged for the same exact fetch if i call the same posts twice in a day?Second question is the one im bent on

Jumping in as one of the makers here - If you are looking at this next to something you already pay for, we would much rather you tell us where we fall short than quietly close the tab. We are a small team and the most useful thing we have ever gotten from a launch is somebody explaining precisely why they did not switch. So push on it today. Ask about the sources you actually need rather than the ones in our screenshots, ask what happens when a site changes, ask what a failed run costs you. The 100% bonus credits run for 24 hours and your first call is free, which is mostly so you can test the reliability claims yourself rather than take our word for them in a launch post. We are in the comments all day, and will give you a straight answer even when it is that we are not the right fit for what you are doing.

Saurabh here, cofounder at Mindcase. Straight question for this thread, since you are the people who would actually use it: what should we build next? We have live library across LinkedIn, Amazon, Google, Instagram, TikTok and YouTube, and almost every one of them exists because somebody asked for it, not because we planned it. So tell me the source you need, the two or three fields you actually care about, and roughly how many rows a month. I will reply in this thread with whether it is straightforward, hard, or honestly a bad idea. Niche is fine. Some regional marketplace or an industry directory nobody outside that industry has heard of is usually more useful to us than another big platform.