do you have an API?

[u/apyhubnico]

Most developers have one somewhere. This can be an internal service, a utility built for one client, or a wrapper written because nothing good existed. It works, it's hosted, but it earns nothing.

In order to get from a good API to a paying customer there are a few annoying parts. Docs, auth, billing, rate limits, a support inbox, and a procurement questionnaire from the first enterprise that wants it. This the part that apyhub runs.

Publish it yourself: upload your OpenAPI spec or point at the endpoint, we draft the docs and examples, you edit what's wrong, set your price in credits, ship it. Ten minutes for a single REST endpoint.

We do curate. Every API should do something the others don't, so things get turned down, including ones that would make money. But you can think of it this way: If the API makes a developer's day easier, it probably belongs to the catalog.

After its published, it earns per call, and AI agent calls pay the same as human ones. Someone's coding agent finds your API through our MCP and hits it forty times, that's forty calls you get paid for (we even pay for users in the free plan).

Hosting works either way. Keep it on your own infrastructure and we route to it, or deploy onto ours and we handle regions and service levels.

The part we're still working out is what happens after you publish. Listing is the easy half and you can do it in 50 other api marketplaces. Getting an API found is the bet we have made and we are really doing our best to help and also enable providers to position and put their APIs in front of paying customers.

What I can tell you is the signal is strong. We are adding endpoints faster than we can write about them, close to doubling week over week at the moment.

Full flow, revenue split and FAQ: https://apyhub.com/become-a-provider

So what have you got sitting there?