Not making a living, but I make about $200/mo from an API that parses recipe ingredients like "2 cups finely chopped onions" into structured JSON.[0] I put it in maintenance mode in 2019, so it's about 99% passive income, as I spend only about an hour or two on maintenance per year. I'm surprised all my clients haven't switched to LLMs, but maybe I still outdo LLMs on price/accuracy since it's so niche. I'd like to s…
Ask HN: Anyone making a living from a paid API?
51–60 of 184 posts
Re: Ask HN: Anyone making a living from a paid API?
#52On the same topic: does anyone have an API concept that they wish existed and that they'd be willing to pay for?
Same thing for home improvement - Lowe’s in stock indicator is wildly wrong to the point that I sometimes call and ask an employee to go physically look at the item.
Re: Ask HN: Anyone making a living from a paid API?
#53Earlier quoted context omitted.
not an api but, Internally we’re just looking for a native text to speach app that auto records all meetings and call a webhook with the transcript. not the notes! for some reason all most rmeetings apps gives you only notes and seldomly a webhook or similar. also not interested in zapier etc. After two weeks off looking for a solution, we’re going to vibe code something basic and use deepgram. If we just skipped the…
Recall.ai is exactly this. Using them at my current company and it works well. It even supports live transcription.
Re: Ask HN: Anyone making a living from a paid API?
#54Re: Ask HN: Anyone making a living from a paid API?
#55Not making a living, but I make about $200/mo from an API that parses recipe ingredients like "2 cups finely chopped onions" into structured JSON.[0] I put it in maintenance mode in 2019, so it's about 99% passive income, as I spend only about an hour or two on maintenance per year. I'm surprised all my clients haven't switched to LLMs, but maybe I still outdo LLMs on price/accuracy since it's so niche. I'd like to s…
Re: Ask HN: Anyone making a living from a paid API?
#56On the same topic: does anyone have an API concept that they wish existed and that they'd be willing to pay for?
Local grocery prices. Let me upload a shopping list and allow me to optimize for cost (visit this store for these items, this store for these items) and a trail to follow through the store for optimal pathing. Same thing for home improvement - Lowe’s in stock indicator is wildly wrong to the point that I sometimes call and ask an employee to go physically look at the item.
Re: Ask HN: Anyone making a living from a paid API?
#57I know of a guy, but his scenario was quite unique. I was working for an energy company who shall remain nameless, but who's internal IT was a tangle of external consultants milking the place for millions, and ineffective/underserved full time staff who couldn't run a query on a database without a change control committee of consultants milking them for yet more cash. Anyway, this guy was the go to guy for gas custom…
> moved the customer data for gas customers to his own system That sounds highly illegal.
Re: Ask HN: Anyone making a living from a paid API?
#58I’d say that this kind of projects are not different than any entrepreneurial endeavor, and the biggest challenge is usually acquisition, even though the technical part was / is hefty too.
Re: Ask HN: Anyone making a living from a paid API?
#59Earlier quoted context omitted.
Browserless can do this for free: docker run -p 3000:3000 browserless/chrome:latest
> instead of managing browser clusters, and handling all the corner cases The cost with running a docker container is you have to manage that container. You’re paying with dev time not money.
Re: Ask HN: Anyone making a living from a paid API?
#60I don't think I'm authorized to share any of the specifics, so will keep it generic.
The API is a world-class machine learning model for a specific scenario. There's a public price list, and various customers manage to negotiate various discounts.
Our biggest challenge is that Google Lens (while much worse than us for our specific domain) is becoming good enough for the average potential customer.
I think one of the regrets is only doing the ML API and not the end-user apps. It turns out the people creating the front end pocket most of the money.