Tech Come Break My API!

[Punyeto]

Beat the shit out of it, but please report back what broke! The address is in my signature. No card required for the trial.

About a year ago I built my first adult site in a LONG while. I had a bunch of sites in college (20+ years ago), the landscape is much different now. I wanted a live cam aggregator site. There are many scripts and plugins for WordPress, but most were made decades ago (and have the looks to match).

I'm a working software engineer. I wound up building my own aggregator API to provide content to the site. Eventually it became what I wish existed when I started. I'm now rolling it out as it's own tool for webmasters. It's fast, modern, and very easy to integrate, but I have questions...

1. IS THIS SOMETHING ADULT WEBMASTERS WANT? It seems ready to go scripts, old looking or not, is what sells. Should I create a companion script to go along with it?

2. WHAT IS A FAIR PRICE AS A SAAS? I'm launching with eight cam sites (Chaturbate, BongaCash, AWSEmpire, and other usual suspects) with more planned weekly post-launch. It's an active project. I want to be compensated, but I'm not looking to knock webmasters over the head.

3. WHAT FEATURES DO ADULT WEBMASTERS VALUE MORE? Additional integrations (cam sites), more/better filters to help niche down, or something else?

[blackmonsters]

Beat the shit out of it, but please report back what broke! The address is in my signature. No card required for the trial.

About a year ago I built my first adult site in a LONG while. I had a bunch of sites in college (20+ years ago), the landscape is much different now. I wanted a live cam aggregator site. There are many scripts and plugins for WordPress, but most were made decades ago (and have the looks to match).

I'm a working software engineer. I wound up building my own aggregator API to provide content to the site. Eventually it became what I wish existed when I started. I'm now rolling it out as it's own tool for webmasters. It's fast, modern, and very easy to integrate, but I have questions...

1. IS THIS SOMETHING ADULT WEBMASTERS WANT? It seems ready to go scripts, old looking or not, is what sells. Should I create a companion script to go along with it?

2. WHAT IS A FAIR PRICE AS A SAAS? I'm launching with eight cam sites (Chaturbate, BongaCash, AWSEmpire, and other usual suspects) with more planned weekly post-launch. It's an active project. I want to be compensated, but I'm not looking to knock webmasters over the head.

3. WHAT FEATURES DO ADULT WEBMASTERS VALUE MORE? Additional integrations (cam sites), more/better filters to help niche down, or something else?

Good luck.
See my sig, and not a single donation for my free script.

[CaptainHowdy]

Good luck.
See my sig, and not a single donation for my free script.

Make a PP payment button to make it easier for someone to donate . . .

[Punyeto]

Good luck.
See my sig, and not a single donation for my free script.

Do you know how many sites are using it? I have two suggestions:

1. Update the UI. People base code quality on UI. Correct or not, it's something we have to deal with. A clean modern UI will help.

2. Add a "Donate Button" that makes it easy for them to give money. Add it to whatever admin panel you created as well. I'm persist it unless they donated actually.

[blackmonsters]

Make a PP payment button to make it easier for someone to donate . . .

Don't think it's a good idea to put a PP button on a site with adult content.

[Huggles]

Bro we used to be able to drunkenly upload a gallery and wake up to $500

[bill_musk]

Beat the shit out of it, but please report back what broke! The address is in my signature. No card required for the trial.

About a year ago I built my first adult site in a LONG while. I had a bunch of sites in college (20+ years ago), the landscape is much different now. I wanted a live cam aggregator site. There are many scripts and plugins for WordPress, but most were made decades ago (and have the looks to match).

I'm a working software engineer. I wound up building my own aggregator API to provide content to the site. Eventually it became what I wish existed when I started. I'm now rolling it out as it's own tool for webmasters. It's fast, modern, and very easy to integrate, but I have questions...

1. IS THIS SOMETHING ADULT WEBMASTERS WANT? It seems ready to go scripts, old looking or not, is what sells. Should I create a companion script to go along with it?

2. WHAT IS A FAIR PRICE AS A SAAS? I'm launching with eight cam sites (Chaturbate, BongaCash, AWSEmpire, and other usual suspects) with more planned weekly post-launch. It's an active project. I want to be compensated, but I'm not looking to knock webmasters over the head.

3. WHAT FEATURES DO ADULT WEBMASTERS VALUE MORE? Additional integrations (cam sites), more/better filters to help niche down, or something else?

CrakRevenues offers that already

[CaptainHowdy]

Don't think it's a good idea to put a PP button on a site with adult content.

https://buymeacoffee.com/ ??

[fris]

i dont see many people paying for this, thats my honest opinion, since all its doing is making a connection to the api itself. so they are essentiually m aking 2 calls. one to your server. and one to the actual api. doing the api call directly will save on requests speed wise.

[lemonlinx]

i dont see many people paying for this, thats my honest opinion, since all its doing is making a connection to the api itself. so they are essentiually m aking 2 calls. one to your server. and one to the actual api. doing the api call directly will save on requests speed wise.

I totally agree

[blackmonsters]

https://buymeacoffee.com/ ??

Checking that out. Thanks.

[Punyeto]

CrakRevenues offers that already

For the cam sites they are affiliated with, yes, but with a few caveats:

- Speed: I actually used their API for a bit when I first started. They had a serious latency problem. Filters made it worse. They're big, so I'm guessing they've worked it out by now. The last time I looked at their docs they mentioned it though. My API is a separate service written in Go. Each node handles ~19,000 requests a second and the infrastructure will autoscale long before it gets to that 19K.

- You have to be their sub-affiliate. If you already have an affiliate account with any of those sites, you can't use it with their API (unless that's changed since I looked at their program). My API will return affiliate links with your respective affiliate IDs. Of course, I'd love for people to sign up via my site, but I built it with the idea of people bringing their own affiliate IDs. Especially with established sites like Chaturbate.

- They have many of the major cam sites, but getting them to add new sites of the fly is unlikely. That's the drawback of being big. I'm actually very interested in integrations. I plan on one a week at least, but can add additional on request.

That said, their filtering is currently more robust. That will change by the end of next week...

[Punyeto]

i dont see many people paying for this, thats my honest opinion, since all its doing is making a connection to the api itself. so they are essentiually m aking 2 calls. one to your server. and one to the actual api. doing the api call directly will save on requests speed wise.

They don't need to make two calls. They make one call to my API, which returns JSON for the rooms they requested (including their affiliate links). Suppose you have an Ebony site. You can make a single API call and retrieve the related rooms across all affiliates. You're free to fashion your UI to embed rooms on separate pages or link directly to the cam site. That single call provides everything you need.

You can use one API to build many different niche cam sites, or niche cam ads on all of your other sites.

That said, you may be right. Maybe no one will pay for it! I use it (and would have gladly paid for it back when I started out), but that value may not translate with others. You don't know until you try, so I am!

[fris]

They don't need to make two calls. They make one call to my API, which returns JSON for the rooms they requested (including their affiliate links). Suppose you have an Ebony site. You can make a single API call and retrieve the related rooms across all affiliates. You're free to fashion your UI to embed rooms on separate pages or link directly to the cam site. That single call provides everything you need.

You can use one API to build many different niche cam sites, or niche cam ads on all of your other sites.

That said, you may be right. Maybe no one will pay for it! I use it (and would have gladly paid for it back when I started out), but that value may not translate with others. You don't know until you try, so I am!

two calls are still being made. one to your server, then your server is making the call itself. not saying the user is making the two calls, but they are being made in the end. and charging $50 a month for api calls that are already free, just doesnt make sense.

nice job on the system though.

[fuzebox]

Anyone that isn't making money can't afford this, and anyone who is, doesn't need it.

[bill_musk]

two calls are still being made. one to your server, then your server is making the call itself. not saying the user is making the two calls, but they are being made in the end. and charging $50 a month for api calls that are already free, just doesnt make sense.

nice job on the system though.

$50 a month? Yeah that makes no sense in this era of Claude code.

[bill_musk]

For the cam sites they are affiliated with, yes, but with a few caveats:

- Speed: I actually used their API for a bit when I first started. They had a serious latency problem. Filters made it worse. They're big, so I'm guessing they've worked it out by now. The last time I looked at their docs they mentioned it though. My API is a separate service written in Go. Each node handles ~19,000 requests a second and the infrastructure will autoscale long before it gets to that 19K.

- You have to be their sub-affiliate. If you already have an affiliate account with any of those sites, you can't use it with their API (unless that's changed since I looked at their program). My API will return affiliate links with your respective affiliate IDs. Of course, I'd love for people to sign up via my site, but I built it with the idea of people bringing their own affiliate IDs. Especially with established sites like Chaturbate.

- They have many of the major cam sites, but getting them to add new sites of the fly is unlikely. That's the drawback of being big. I'm actually very interested in integrations. I plan on one a week at least, but can add additional on request.

That said, their filtering is currently more robust. That will change by the end of next week...

Their speed is correct.

Their filter is correct

They have 11 cam sites. You propose 8?

And while it's true you have to go through their afilliate partnership, anyone who makes enough money will be able to recode this with Claude and save 1 API call by going starit to the provider?


I'm all for bringing new tools to the market, but they have to be fair priced and add real values.

[fris]

Their speed is correct.

Their filter is correct

They have 11 cam sites. You propose 8?

And while it's true you have to go through their afilliate partnership, anyone who makes enough money will be able to recode this with Claude and save 1 API call by going starit to the provider?


I'm all for bringing new tools to the market, but they have to be fair priced and add real values.

i have my own cam api for wordpress and php standalone, and even i dont wrap it in a my own server call. i always make my calls directly to the api for the end user. one for privacy reasons as i dont want them hitting my server

[grzepa]

Claude does not allow any adult stuff

[bill_musk]

Claude does not allow any adult stuff

yes it does. I probably already build 60 adult projects with it.

[fris]

Claude does not allow any adult stuff

if claude code is not allowing you to do it, treat the api description as something other than a porn or webcams api.

[V_RocKs]

Claude does not allow any adult stuff

I have used it with adult plenty of times. And when that doesn't work, I move that piece of the project over to venice.ai and it does that part of the project.