Live data from Hacker News

Building a starter pack for an API-as-a-Service

resteasyapi.com

11–20 of 28 posts

Re: Building a starter pack for an API-as-a-Service

#11
post #7
post #5

I sell an API as a service,[0] and I've been using RapidAPI for years. I've never been happy with them. They charge a 20% fee, and then there's another 3-5% fee for payments via PayPal. And they do many small transactions per month, so you pay PayPal's minimum fees over and over, making the total fees about 25-30%. On top of that, their service is terrible. Customer support is rarely helpful, they frequently fail to…

Tying in paddle as merchant of record for all installs shouldn’t be that challenging no? Stripe has connect as well to split but I’m not sure their merchant of record features are as mature.

>Tying in paddle as merchant of record for all installs shouldn’t be that challenging no?

It's not that hard, but I'm anticipating like 40 hours of work start to finish to get Paddle set up and write the integration.

The one positive thing I'll say about RapidAPI is that they made onboarding easy. They handle all of user signup, payments, etc. and they just forward your API requests from users. The only code I had to write is a few lines to populate a custom HTTP response header to tell RapidAPI how many units of my service the request consumed.

Paddle provides a lot less infrastructure, so I still have to write my own user signup flow. Paddle offers a JS library that does the heavy lifting for user signup, but I still have to integrate it with my website. And then they don't have the proxy model at all, so users talk directly to my backend, and my backend has to check with Paddle to see whether the user is valid or not. Then my backend has to both respond to the user and send a separate request to Paddle to add to the user's bill.

>Stripe has connect as well to split but I’m not sure their merchant of record features are as mature.

I didn't realize Stripe offered MoR at all, but it looks like they do now. My reading is that if I were to sell under RestEasy, then Stripe would indeed act as my MoR because I'm the "third-party seller":

>Is Stripe a merchant of record?

>Stripe is an MoR, but only for its Stripe Connect platform. With Stripe Connect, businesses can create platforms or marketplaces that process payments for third-party sellers. In this case, Stripe serves as the MoR, processing payments and assuming the associated responsibilities on behalf of the third-party sellers.

>However, when businesses use Stripe to process payments for regular direct transactions, the business itself remains the MoR while Stripe acts as a payment processor or payment gateway. This means that the business is responsible for transactional compliance, tax obligations, and managing refunds and chargebacks, while Stripe handles the technical aspects of transaction processing.

https://stripe.com/resources/more/merchant-of-record

Re: Building a starter pack for an API-as-a-Service

#17

are there any open source solutions in this space? something that sits in front of your API as a proxy, and has an interface for managing access, rate limits, billing etc - with simple deployment to a cloud provider?

If your provider support docker I suggest you go with Apisix, I found this article pretty useful following that path: https://blog.frankel.ch/poor-man-api/

Re: Building a starter pack for an API-as-a-Service

#18
post #17

are there any open source solutions in this space? something that sits in front of your API as a proxy, and has an interface for managing access, rate limits, billing etc - with simple deployment to a cloud provider?

If your provider support docker I suggest you go with Apisix, I found this article pretty useful following that path: https://blog.frankel.ch/poor-man-api/

AFAIK, https://apisix.apache.org does not have a billing / monetization feature

Re: Building a starter pack for an API-as-a-Service

#19
post #2

I am cofounding a new SaaS "starter pack", but for a very specific niche. This product aims to serve as the frontend and middleware for anyone planning to launch an API-as-a-Service product. The idea for this product is straightforward: once you've built an awesome API service and are ready to share it with the world, you've only done like 20% of the work. You need to build an entire UI so that your customers can cre…

So there is no actual functionality to try out right now? From what I browsed, the site is essentially a landing page + email signup.

Correct. Sorry to disappoint, but we're very early stage at this time. We'll be releasing more info as we develop the product and collect feedback.

Re: Building a starter pack for an API-as-a-Service

#20
post #17

Earlier quoted context omitted.

If your provider support docker I suggest you go with Apisix, I found this article pretty useful following that path: https://blog.frankel.ch/poor-man-api/

AFAIK, https://apisix.apache.org does not have a billing / monetization feature

True, there is not a built-in feature for billing. It'd be necessary to build on top of apisix, using itsmetrics (via prometheus) and consumer groups
Post reply on HN