Upfront: I’m a co-founder of ApyHub. I am looking to grow the number of APIs and endpoints on the platform. That’s my primary interest here, read everything with that in mind.

Some of the best APIs I have seen are built by one person solving one problem extremely well. This can be anything, a holiday data service. A screenshot renderer. A receipt or a cv parser. Technically solid, running for years, and almost nobody knows they exist. The builder is busy maintaining it. Distribution is a different job they never signed up for.

That’s the job we took on. We cover the entire layer from API discovery to consumption. Here’s what that means for a provider:

  • Distribution. One subscription gives our users the whole catalog, so your API is available to every subscriber the moment it goes live. No marketing site, no SEO grind.

  • MCP by default. Every endpoint is agent-ready. Claude, Cursor, any agent runtime can discover and call your API without you writing glue code.

  • Fair, transparent payouts. You set your own price and change it whenever you want (dynamic pricing). Clean split, monthly payouts, no hidden fees. You keep your IP, no exclusivity.

  • Hosting. Keep running it yourself and we route to it, or we host it on our infra and take ops off your plate.

  • We handpick and verify every service before it lists. That’s the whole point.

Publishing takes under 10 minutes, I swear.

If you have built an API, what would stop you from listing it somewhere like this? Loss of control? The split? Trust?

Something else? I want the objections as much as the signups. :)

  • fuzzzerd@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    15 days ago

    Its cool you have devs already subscribing, so there’s a built in audience; however, I have no idea if your existing audience has need of my service and by extension whether listing with you is a good idea for me or not.