Jarvee current twitter rate limits?

fungames

Regular Member
Joined
Mar 16, 2009
Messages
282
Reaction score
101
I saw v1.1 x.com api writes was like 2400/day for automation from official twitter v1.1 api according to chatgpt. You could buy enterprise plans or just make multiple api accounts.

However, JarveePro does not use official v1.1 api according to GPT, it uses user simulation. What kind of limits are people getting using Jarvee with x/twitter? Obviously it will be more than 2400/day, I would think? Also, won't x just limit/reduce the # of writes per day from normal users once v1.1 gets discontinued anyways? Making it an IG botting nightmare all over again? Or have they already been reduced/limited since the launch of v2? Is anyone botting x right now and can chime in?


Thanks, very much,
Fungames
 
Gotta remember ChatGPT sometimes straight-up just makes stuff up. Depending on what it is exactly, 2400 per day on any action on Twitter, as far as I'm aware, is vastly over most of the allowed limits. Might vary depending on what level of account you have (free, premium, etc.).
 
Gotta remember ChatGPT sometimes straight-up just makes stuff up. Depending on what it is exactly, 2400 per day on any action on Twitter, as far as I'm aware, is vastly over most of the allowed limits. Might vary depending on what level of account you have (free, premium, etc.).
Yea, well, even if you don’t use official api, they are still going to rate limit you. I think the 2400/day was from twitters official site. I thought I spoke to jarvee too and they said they used their own private wrapper.

It’s going to be even worse when 1.1 becomes retired. I think it was like $100/month for 3000 writes/month lol. Then like $5000 a month for pro at 300,000 writes/month. Lol.

Private wrappers won’t really help either, they will just rate limit you if you are not paying for the official api. Ugh!
 
I'm using SuSocial (basically jarvee). It has been slow for me. First it only scraps 50 accounts at a time (at least what it says), when I go to the extraction list some of those disappear. Then follow/unfollow is a hit or miss, sometimes it gets stuck, but overall is very slow and unstable.
 
Using Jarvee's user simulation can bypass API limits, but it carries risks of detection and account suspension. X may indeed reduce write limits in the future, especially with the transition to v2, which already enforces stricter policies. Current botting limits are harder to gauge but are generally lower and more stringent than before.
 
Back
Top