"2CB16598-CB82-4CF7-B332-5990DB66F3AB": [
      "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36"
    ],
    "0152B4EB-D2DC-460A-89A1-629838B529C9": [
      "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36"
    ],
    "867D55F2-24FD-4C56-AB6D-589EDAF5E7C5": [
      "Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Mobile Safari/537.36",
      "Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Mobile Safari/537.36",
      "Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Mobile Safari/537.36"
    ]

Working with these user agents has been fixed again. Some new improvements and fixes have been made, taking into account the error logs that have been accumulating in Solver for a long time.

Client servers are expected to be reset.

Updates have been completed.

"867D55F2-24FD-4C56-AB6D-589EDAF5E7C5": [
      "Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Mobile Safari/537.36"
    ]

Periodic maintenance was performed, and the calculation issue in the bio was fixed.

"867D55F2-24FD-4C56-AB6D-589EDAF5E7C5": [
      "Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Mobile Safari/537.36",
      "Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Mobile Safari/537.36",
      "Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Mobile Safari/537.36"
    ]

This site key and these user agents are temporarily suspended.

“2CB16598-CB82-4CF7-B332-5990DB66F3AB”: [
      "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36"
    ]

Please use this site key and this user agent to register on Twitter.


In addition, just like your Android requests, the TWITTER_REGISTER feature has been enabled in the blob section.

Here is an example:

{
  “ApiKey”: “YOUR_API_KEY”,
  “Blob”: “TWITTER_REGISTER”,
  “UserAgent”: “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36”,
  “Proxy”: null,
  “SiteKey”: “2CB16598-CB82-4CF7-B332-5990DB66F3AB”,
  “SiteUrl”: “https://x.com/i/flow/signup”
}

Sample response output; 

{
  “success”: true,
  “taskType”: “SUCCESS”,
  “token”: “...”,
  “solverDetails”: {
    “flow_token”: “...”,
    “cookie”: “{...}”,
    “useragent”: “...”,
    “sec-ch-ua”: [...]
  }
}

All client servers are being restarted. This will take a few minutes.

“2CB16598-CB82-4CF7-B332-5990DB66F3AB”: [
      "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36"
    ]

A minor mbio correction was made.

All client servers will be ready in approximately 5 minutes.

Reg Under maintenance. Unlock Active

Reg is active again. Use Chrome version 137!

Reg and unlock active. Chrome version 138 added! (Only Web)

all servers are overloaded. main server, restapi and client servers will be restarted.

restapi restarted.

overloads issue fixed.

the proxy provider is doing an update to speed up its server (about 5 minutes.) during this time you may not get a response to your requests.

Periodic maintenance work is being carried out on the solver.

Reg and unlock active🔥

Chrome version 138 is more stable than others. I recommend using 138

Some updates are being made to the solver. During this time, you may not receive a response to some of your requests or you may experience delays.

A new method has been added to the Createtask method;

{
  ‘ApiKey’: ‘YOUR_API_KEY’,
  ‘Blob’: ‘TWITTER_REGISTER’,
  ‘UserAgent’: ‘POOL’,
  ‘Proxy’: null,
  ‘SiteKey’: ‘POOL’,
  ‘SiteUrl’: ‘https://x.com/i/flow/signup’
}

Due to high demand, the pool system will be reactivated. We are currently conducting the necessary tests. API security has been enhanced. Although our DDoS prevention method has been effective recently, some individuals continue to attempt new methods. We are monitoring and observing you. The API's security layer has been elevated to a higher level, and a core update has been implemented.

The restapi will be updated after testing. We are reviewing the tests we have conducted.