Preparation

Buying accounts

What to look for in accounts and sellers, and how to test a new batch before you buy more.

01What to buy

Accounts are the one part of the setup you cannot fix later. Buy by the criteria below, test a batch of 30, and only buy more from a seller whose batch held up.

Required - skip any offer that misses one

tdata format. See the next section for why.
Aging. The longer the accounts rested after registration, the better.
Not sold before. A resold account may still be logged in somewhere else.
No spamblock. An account that is already limited is no use for commenting.
Country you can match. You will need a proxy in the same country as the account's phone number.
No 2FA password, or the password from the seller. Telegram may ask for the current password when Account Protection creates a new login.

Avoid

Sellers with many negative reviews. Thresholds are below.
Resold accounts. Someone else may still hold a working login.
Accounts with an unknown 2FA password. You will not be able to secure them.

02tdata or session

Buy tdata. It is the folder Telegram Desktop keeps for a logged-in account, and it is what ATREOX imports in bulk: one .zip with a folder per account (zips per account inside it are fine), up to 100 accounts per import.

A session string can only be added one account at a time (Import accounts → Single import), together with its api_id and api_hash.

tdata also lets you log an account in again later. If its session ever dies, Recover from tdata in Account Manager creates a new one. A bare session string cannot be recovered this way.

03Choosing a seller

Seller ratings on account shops are almost always close to perfect, so ignore the score. Open the seller's profile and count the negative reviews.

Negative reviews	Verdict
Up to 3	Ideal
Up to 10	OK
Up to 50	Acceptable
51 to 100	Worse than average
Over 100	Stay away

Then look at aging. Between two sellers with a similar review count, pick the one whose accounts rested longer. Treat the aging figure as the seller's claim, not a fact: the last section explains why.

04Testing a new batch

Start every new seller with a test batch of 30 accounts and give it two weeks before you buy more.

Import the batch with one proxy per account. Under About this purchase, fill in Seller and Layover (the aging the seller claimed). They can only be recorded at import, and they are how you compare sellers later.
Select the new accounts and run Checks → Check health and Check capability.
Week 1: put the accounts in Active Warmup and run the protection steps from the Account Protection guide.
Week 2: add them to Neurocommenting with a limit of 3 comments per account per day. Raise the limit by 1 every day.
Compare batches in Account Manager → History: how many are still alive, frozen or unable to post, per seller.

Account Manager History tab: the Batches table with seller, layover, bought, alive, frozen and cannot-post counts per import — History → Batches: how each batch is doing, per seller.

The comment limit is a daily limit. It resets at 00:00 UTC, and accounts that reach it resume on their own after that.

Active Warmup → Account Protection →

05What our aging test showed

We bought two batches on the same day, from two sellers, and ran them with the same proxy setup and the same warmup. One seller advertised a long aging period; the other claimed none. Within a week most of the long-aging batch was frozen, without having posted a single comment. The other batch held up.

A seller's aging claim on its own does not tell you whether the accounts will last.
Accounts that freeze while doing nothing arrived that way. That is the seller, not your setup.
Accounts that look fine while resting are not proven good yet. Problems often show up once they start working.
One bad batch from a usually decent seller looks exactly like a bad seller. Test every batch, not just every new seller.

Next: Proxies →