| Nadles | RapidAPI | |
|---|---|---|
|
Business model |
Monetization solution |
API Marketplace |
|
Payment options |
All payment methods supported by Stripe and Paddle |
PayPal |
|
Transaction fees |
0% |
20% |
|
Merchant of Record option |
Yes You can use Paddle for payment processing and global tax compliance. Nadles augments Paddle with usage-based pricing models. |
No It's your responsibility to ensure compliance with Sales tax/VAT/GST regulations. |
|
Listing on a marketplace |
No
We onboard customers from your landing page.
|
Yes Your API neighbors with a lot of low-quality APIs, ranged by obscure algorithms based on unknown metrics. |
|
Hosted checkout pages |
Yes Nadles offers hosted checkout pages with fully customizable style, where your customers can subscribe, pay and start using your API. |
No Your customers have to deal with the standard RapidAPI catalog. |
|
Free-form products |
Yes Create as many products as you need, name and configure them your way. |
No There are 4 standard plans that you can configure: Basic, Pro, Ultra, Mega. |
|
Tiered pricing models Different prices for different usage tiers. |
Yes Among others, Nadles offers graduated and volume-based pricing models. |
No |
|
Billing cycle How often you can charge your customers |
Any
You can bill your customers on an arbitrary schedule. |
Monthly/daily |
|
Billable metrics What you can charge for |
Anything API calls, sent SMS, processed images, ChatGPT tokens, credits, etc. |
Anything |
|
Usage metering conditions |
Any arbitrary condition You can flexibly configure, in what cases Nadles should record usage. The usage condition can be based on any request and response attributes. |
No RapidAPI records usage for all response codes less than 500. |
|
Custom terms per customer |
Yes You can fully customize product terms for individual customers. |
Yes You can create private plans and invite specific RapidAPI users to subscribe. |
|
Configurable spend limits Protect your customers from overages. |
Yes |
No |
|
Adjustable purchase quantity Let customers configure their subscriptions. |
Yes |
No |
|
Product templates Use pre-defined templates to create your API products in seconds. Customize them as needed. |
Yes |
No |
|
Limited seats Limit maximum number of subscriptions to a product. |
Yes |
No |
|
Product-scoped request and response transformations |
Yes Use JavaScript or jq to write complex transformations. |
Basic You can add, replace, remove attributes in requests and responses. |
|
Meter once Record usage only once for API calls with the same parameters. |
Yes |
No |
|
Product-scoped access rules You can decide which endpoints to include in the product. |
Yes |
Yes |
|
Product-scoped rejection rules Make API gateway drop certain requests based on request attributes. |
Yes |
No |
|
No-code You can start selling your API with several mouse clicks. |
Yes |
Yes |
|
Best for |
Small and medium-sized enterprises and individual entrepreneurs looking to reduce their time to market |
Developers who want to "submit and forget" |
Try Nadles for 14 days. No credit card required.
Free trial for 14 days →© Leotech s.r.o., 2022-2024. All Rights Reserved.
This feature allows you to modify requests and responses if the current user is subscribed to a certain product.
Use case examples:
perPage query string parameter to always be 10.
X-Job-Timeout: 10s to each request for Basic product,X-Job-Timeout: 600s to each request for Premium product
and use these values in your API to set different timeouts for users with basic and premium subscriptions.
X-Enabled-Features: to each request, check it on the API side and enable or disable features for the current user accordingly.
Say, you have two endpoints:
And you want to charge your customers only for the first time they retrieve the results, as the subsequent calls will be served from cache.
Using "meter once" feature, you can make Nadles do exactly that: record metered usage only for the first call to the result retrieval endpoint.
You might want to run a promo campaign with a limited number of seats available.
Limited offer! $20 per month instead of $99. 100 seats available.
Using Nadles checkout links, you can limit the maximum number of subscriptions made via that link, which makes it trivial to run promo campaigns like that.
Spend limits allow you to protect your customers from accidentally overusing your API.
A mistake in the application code or a malicious user trying to abuse the app can cause hundreds of thousands of unexpected API calls resulting in a huge bill for the customer.
With spend limits, customers still pay for what they actually use and can set the maximum usage limit to protect themselves from huge bills — the API gateway won't let them make more calls than configured.
You can configure the spend limit for each product and each customer individually.
You can also allow your customers to adjust the maximum usage limit on their own during the checkout.
You can let your customers change the included volume of API calls (or other billable metrics) when they make a purchase.
This allows them to pick the most comfortable terms, get volume discounts if you offer tiered pricing (the bigger the purchase volume, the lower the price per unit) and have more control over their costs.
Rejection rules allow you to model your API products more precisely by dropping certain requests based on request attributes.
Use case examples:
Allow USD to EUR currency conversion only.
Reject request if query string param "from" is not USD or "to" is not EUR.
Allow maximum of 10 elements submitted via a batch endpoint.
Reject request if JSON request body field "items" is longer than 10 elements.
Allow maximum of 1000 characters in a request to a Text-to-Speech engine.
Reject request if query string param "query" is longer than 1000 characters.