Well make sure your connections are set to the same or less then the total number of apis you have of course. I think it will limit it if not, but I woudl do that anyway.
As for going faster moz actually allows you to get the data from up to 10 urls on 1 api query. So when the page authority addon was updated it was rewritten to allow it to get 10 urls data on 1 query. So if you have 70 apis at 70 connections its getting 700 urls worth of data, then delay 10 seconds then 700 more. So 30 seconds or there abouts and it could churn thru 2000 urls.
Do all your apis give the 429 or only some of them?
Also I have heard a few people say they got their accounts blocked. My guess is when moz finds a footprint like multiple accounts created from the same domain or same ip etc... So its possible they picked up on a footprint for a bunch or all of your apis that allowed them to link them together and then that would violate their TOS so they banned them all.
I normally keep the number of connections at 100 or so (it never made any difference all these years) but I tried reducing it to less than 20 connections too. But did not make any difference and the Error 429 kept reoccurring.
I never knew about the 10urls per API query. Yes, it was probably 10 times faster now with the new version of the PA addon. For large lists, it took upto an hour in the past. But I tried large lists once or twice after the latest update and it used to complete in a 5-10 minutes. Perhaps even faster than the Social Checker or other addons.
Almost all of them give 429 .. sometimes a few give 403 or Error with no number (12030 in API logs below) in between .. and sometimes very few names in the list get their actual PA values. For example, in a 2000 list for example, I might suddenly have 40-100 with actual PA values randomly instead of Error 429 or other Errors. Initially, the new version of the plugin was working very well and all of them were showing PA values and that too extremely fast as mentioned earlier. The problem has occurred only in the last week or so (I am not too sure about the exact date as I had not checked much PA recently)
I had created all Moz accounts with different IPs and different emails and different logins etc. to remove all footprints. And they have been created over the years. Yes, a few accounts seem to get banned at times but the ones I am referring to work fine in other PA dependent addons such as the Expired Domain Finder plugin.
In fact, I ran the newest version PageAuthority Addon right now once again to test out. I pasted around 40-50 URLs to test out. Today in the first run, it suddenly checked them all fine the first time in an instant. So, I was surprised and then ran another set of 40-60 sample URLs. This time, it showed 429 Error once again with a few Error (no error name mentioned) and showed "Error Receiving Data (12030): The connection with the server was terminated abnormally" in the API logs below. Then I reran the first set of URLs to check if they get checked and is it related to domain etc. But the original set of 40-50 URLs (that was checked fine the first time) again showed the same 429 Error. I tried many times with different sets of URLs and it was Error 429 almost each time. Only once or twice there were like 10 results checked from the sets (as I had mentioned above I often used to get say 40-100 results sometimes out of 2000 URLs for example). Today, I noticed clearly and realized that the urls with results were consecutive i.e. one after another. I calculated and realized that it was 10 results each time with Error 429 before and after that. So, it seems all of those sets of results were with some of the APIs which just got through somehow.
Right now, I made one more test. I picked up an API which was giving Error 429 in the latest test and another API which was giving "Error Receiving Data (12030): The connection with the server was terminated abnormally" in the latest test URL check. Then I opened up Expired Domains Finder Addon and deleted the existing Moz APIs there and inserted the Error 429 API instead. Then I scanned a domain for expired domains and soon, it picked up 20-30 expired domains. I let it run as it waits 10 seconds for the Moz checks. And after sometime it checked all the Moz stats with that Error 429 API inside Expired Domains Finder Addon. After that, I deleted that API from the addon and inserted the "Error Receiving Data (12030): The connection with the server was terminated abnormally" API instead. I again scanned for expired domains and it again found some expired domains and the same 12030 Error Moz API checked all the stats (with the 10 seconds wait time of course). So, the APIs are working it seems but just not in the new PageAuthority Addon.
I am not sure what is creating these Error 429 and 12030. I am not sure if it is due to Moz or due to the addon. I would probably try to create a new set of Moz APIs to check if it is due to the current APIs. Anyways, I have found my own trick to bypass the Error 429 issue for now though it is not that fast. I would not reveal it here as it might be a loophole which might be misused and might stop working once I mention here and everyone uses it. As for a new set of fresly created APIs, I will inform you in the near future once I create a new set of Moz APIs and test with the same.
On a side note, I opened up the Expired Domains Finder Addon probably after several weeks today. I noticed that there is now the option for Majestic metrics too. So, I entered Majestic email and password (Silver account if that makes any difference) which I personally checked in browser before inserting and has got more than half of the monthly subscription limits available. But all the four Majestic fields for the expired domains are showing 0. I clicked on the "Majestic Metrics" button at the bottom and it still it showed all Majestic fields 0. I knew that it was not possible most high DA domains at least have some TF and CF. So, I checked manually and almost all of them have more than 0 TF and 0 CF. Not sure why the Majestic metrics is not working. One thing I would also like to ask is that how many Majestic units does each check cost. Majestic has changed their way of calculating points nowadays. For example, inside the TF CF bulk checker in Majestic.com, they charge 200 units per URL|root|subdomain if the URLs are copy pasted into the checker. But if you create a text file with the same URLs and upload it there in the bulk checker it only costs 10 units i.e. 20 times less. They seem to have now made different ways of charging units depending on the way it is checked. So, how much does this Scrapebox Expired Domains Finder cost. It does not matter much it seems as it will only check the confirmed expired domains which are less than a few hundred domains probably in each scan but still it would be good to know. I am including the Expired Domains Finder in my last test run where the Majestic stats are all 0 as you might notice.