Quote:
Originally Posted by Punyeto
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.