Hey everyone,
Over the past few weeks while building side projects, I kept running into the same issue — finding APIs that actually work takes way more time than it should.
Most of the time:
docs look great, but responses don’t match
you have to test multiple options before finding something usable
marketplaces feel too crowded and hard to filter
After dealing with this repeatedly, I decided to try something simple.
I built Apives — a small platform focused on making API discovery easier and more practical.
The approach I’m experimenting with:
curation over volume → fewer APIs, but more useful ones
real-use focus → things you can plug into actual projects
simpler discovery → not just categories, but use-case driven
Also added a couple of early ideas:
providers can submit their APIs
everything goes through a basic manual check before listing
Right now it’s still very early and evolving.
Not trying to build a massive directory — more like a place where you can quickly find something that works without wasting hours.
Would really appreciate honest feedback from people here:
Does this solve a real problem for you?
How do you currently find and evaluate APIs?
What would make something like this actually useful?
Happy to share more details if anyone’s interested 🙌
Yeah, this definitely resonates — finding APIs that actually work as expected is way more painful than it should be. The docs vs real response mismatch alone wastes hours.
I like the ‘curation over volume’ angle — most directories try to list everything, but as a developer you really just want something reliable you can plug in without second-guessing.
One thing that could make this even more useful: showing real usage signals (like ‘tested recently’, response consistency, or small code examples that actually ran). That would instantly build trust.
Also sharing something I’m building in parallel — You have an idea. $19 puts it in a real competition. Winner gets a Tokyo trip (flights + hotel booked, minimum $500 guaranteed). Round just opened, so best odds right now: tokyolore.com
The problem you're solving isn't discovery, it's verification. Most API directories stop at "here's what exists." You're adding "here's what actually works." That manual check before listing is the real value, not the curation. The question is whether you can scale that check without turning it into a rubber stamp. Once it becomes automatic, you're just another directory. The friction is the feature. Keep it.
Honest feedback: the curation angle is the right bet, but the moat is fragile unless you build something directories can't copy. What if the value was less 'curated list' and more 'tested + verified with real response samples'? Showing actual API responses for common use cases would save way more time than good filtering alone.
Such a great product 👏, appreciate it ☺️