2
3 Comments

Launched a small tool for API discovery — would love feedback

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 🙌

on April 10, 2026
  1. 1

    Nice, congrats on launching 🙌

    Quick question — how are you planning to handle support once users start coming in?

    I didn’t expect it to get messy this early on my side, even with low volume.

    1. 1

      Thanks so much for the kind words and for the great question!

      That's something I've been thinking about a lot. Right now, in these very early stages, support is 100% manual and handled by me personally. The idea is to have a direct line to the first users to understand their pain points deeply.

      My plan is to use these initial conversations to build out a solid knowledge base and FAQ. The goal is to solve problems proactively through better documentation and platform clarity, which ties back to the core mission of Apives.

      And you're so right about it getting messy, even with low volume! I'm trying to be intentional about it precisely for that reason. Curious, did you find any specific tools or methods that helped you manage it when you were starting out?

      Really appreciate you bringing it up. It's a super important point.

      1. 1

        yeah that makes a lot of sense , those early conversations are gold

        what I found is it’s not really about collecting more feedback (that part is easy), it’s more about making sense of it after

        like once you’ve had a bunch of those conversations, it gets surprisingly hard to connect the dots and see what actually matters

        that’s actually what I’ve been exploring, something lightweight that helps surface patterns from those early messages without losing the raw input

        curious how you’re planning to keep track of everything as those conversations grow?