this post was submitted on 22 Jul 2026
2 points (75.0% liked)

Programming

27859 readers
452 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS
 

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. :)

top 1 comments
sorted by: hot top controversial new old
[–] verstra@programming.dev 5 points 6 days ago

Wait, is this a proxy to my API? If yes, what's the privacy policy / do you think users and providers would trust you with sensitive data (that might be subject to local privacy laws). If no, how can users buy access to my API though your platform?

Also, what kind of APIs are supported? REST (HTTP+JSON)? JSON-RPC? gRPC? Capnproto?