I will set up your own bespoke, OB2 config-based, account live-checking system -- Setup in your premises -- Suits your precise needs!

[Clout]

Hello,

 

I have decided to vastly improve and sell the ground-breaking tech used for live-checking in the AccountX.to project, which I was the sole developer of.

 
I have written a program that when supplied with an OB2 config, a combo, and (if needed) proxies, returns whether the given account is alive or not.

 

Everything has been rewritten from the bottom upwards to allow for the biggest degree of freedom and speed.
 
The program is setup as a web-server, which allows it to be used in many different contexts for different usecases.
 
The config-combo-proxy data is submitted as a POST request to a server, and the response is a JSON string with details about the account, whether it is alive or not, etc.

I am not just offering the program here, but instead offering the program as well as its integration to your current account sales setup.
 
That means, I can seamlessly integrate it to your Shoppy/Sellix shop, to your account generator website, to your own website, or any other situation you may be in.
Note: I will not agree to just giving out the software. I am not selling the code itself, I am selling the integration of live-checking to your service.
 

Performance-wise, the program has a 10-20ms overhead over the normal amount of time taken for OpenBullet to run, and it also is completely thread-safe.

 

The whole point is that you can use any OpenBullet config to check the account, meaning no exorbitant fees to coders to write the checker in whichever language your backend is in.

 

If the config is broken, you fix it. You test it. It works. 

 

When I'm done with the setup, I will not need to access the server again for any reason except for any feature additions. The point is that the owner is given the freedom to make his own checkers.

 

No programming experience necessary.

 

Also, everything will be setup on your own hardware (RDPs, VPSs, etc.) and as mentioned completely integrated in your current system.

 
Example of how it works: 

Spoiler

 
POST request to web-server:

POST /check/ HTTP/1.1
Host: localhost:8000
Content-Type: application/x-www-form-urlencoded
Cache-Control: no-cache

checkerToUse=returnsTrueWithDelay&comboToCheck=test%3Atest2

Server Response:

{"comment":"Combo works","httpCode":200,"isChecked":true,"isWorking":true,"combo":"test:test2","combosTested":1}

Note: you do not see any security precautions here because they will absolutely change depending on the project and use.

For example, Shoppy.GG sends webhook requests only through 1 IP, which in case of a Shoppy store, I would only allow access to the server from that IP.

 

Of course, everything can be modified to fit your exact situation.

 
Contact: Telegram , Discord at Clout#3549

Note: Telegram will get you the quickest response. I always prefer Telegram.

[HomesickForUs]

Clout HQ dev, putting in quality and attention to detail into his work! Huge vouch for my guy! 

[Skrippy]

[Clout]

Im online and can start talking to you right now!

[Clout]

online and talking with customers

[Clout]

online and talking with clients!

[cardmani]

GLWS

[Clout]

This is a bump

[Clout]

This is a bump

[Clout]

This is a bump