SMS API Autoreg, SMS Emulator, Real Device SMS Explained

In the Nordi catalogue the word SMS stands in exactly three registration-method labels: SMS API autoreg, SMS emulator autoreg and Real Device SMS. All three report one and the same event — when the account was created, the phone number was confirmed by a code; they differ in what exactly received that code. The labels API autoreg, Mobile API autoreg and Mobile autoreg contain no word SMS at all, and confirmation of a number is not declared in the name of such positions. As of the snapshot of 19.08.2026, 13 positions out of 54 carry a label with the word SMS.

Three labels that contain SMS

SMS API autoreg — the code was received inside an automated process

The most frequent of the three: 7 positions, prices from 15.52 ₽ to 35.26 ₽, total remaining stock 39 865 accounts. The number was confirmed by an incoming SMS inside an automated registration flow. The label is not tied to age — it stands both on the fresh batch «Reg. 08.2026», and on «Aged 2+ months | Reg. 06.2026», and on the older «Reg. 03.2025» and «Reg. 28.05.2024». Six positions out of seven additionally carry the 2FA label, five have the delivery format Login:Pass:2FA_code | Cookie, one IAM, one IGAM. Six of the seven lie in the section Auto-registered accounts with aging, the seventh is the fresh batch «Reg. 08.2026».

SMS emulator autoreg — the code was received by an emulator, not by a SIM card

There is one such position in the stock: «Instagram | SMS emulator autoreg | Fresh | Format: IAM», 15.09 ₽, 599 left, minimum batch 50. The label reads literally: the confirmation code was received by an SMS-receiving emulator and not by a physical SIM card. That is, confirmation of the number during registration did happen, but no live SIM stood behind it. The label carries no other information: the age of the batch is set by the «Fresh» block, and the composition of the delivery by the «Format: IAM» block. The position lies in the section Fresh auto-registered accounts next to the ordinary API and mobile batches.

Real Device SMS — a real phone and a real SIM

Five positions, from 26.50 ₽ to 41.41 ₽, total remaining stock 192 299 — by volume this is the largest of the three SMS labels. Registration ran from a real device, and the number was confirmed from a real SIM card. Only this label states a country in the name: Brazil and Colombia at 26.50 ₽ each, the Philippines and Thailand at 28.15 ₽ each, MIX at 41.41 ₽. All five batches are marked «Fresh», the format for all of them is Login:Pass | Cookie, the minimum batch is 50. Look for them in the section Instagram from real devices — the same section holds three Real Device batches that have no SMS in the name.

Which stock positions carry an SMS label

The full list as of the snapshot of 19.08.2026. The names are verbatim from the feed; the opening block «Instagram |» and the label itself are moved into separate columns.

Labels without SMS: API autoreg, Mobile API autoreg, Mobile autoreg

The remaining registration methods do not contain the word SMS in the name. This is a description of what is declared in the listing:

• API autoreg — 25 positions, from 7.27 ₽ to 120.11 ₽: the largest family in the catalogue, from fresh ones to «Aged 2012–2020».
• Mobile API autoreg — 5 positions, from 6.71 ₽ to 36.43 ₽; “Mobile” marks a mobile registration flow.
• Mobile autoreg — 1 position: «Fresh | Format: Login:Pass | Cookie», 8.52 ₽.
• Real Device — 3 positions, from 10.65 ₽ to 40.90 ₽: a real device is declared, there is no separate SMS note in the name.

The method label is one block of the name out of several, and it has to be read together with its neighbours. In the line «SMS API autoreg | Aged 450+ days | V3 | 2FA | With Email | Format: Login:Pass:2FA_code | Cookie» there are five independent facts — method, age, batch version, 2FA and an email included in the set. One block does not replace another: SMS API autoreg says nothing about age, and «Aged 450+ days» says nothing about the method of confirmation.

The number is not part of the delivery

An SMS label describes an event at the moment of registration, not the contents of an order. The phone number is not handed over to the buyer and does not stay with the account. This is checked by the «Format» block, which lists the composition of the delivery: the catalogue contains Login:Pass | Cookie, Login:Pass:2FA_code | Cookie, IAM, IGAM and IAM (No Cookie) — not one of them has a field with a phone number. When an email comes with the account, that is put in a separate label: «With Email», «Gmail», «Firstmail», «Email confirmed». No analogous label for a phone exists in the catalogue. That is why SMS API autoreg, SMS emulator autoreg and Real Device SMS are worth reading as information about the origin of a batch — part of its passport — and not as access to a number.

Summary

The three labels with the word SMS answer one question — what received the confirmation code at registration: an automated process (SMS API autoreg, 7 positions), an SMS-receiving emulator (SMS emulator autoreg, 1 position) or a real phone with a real SIM (Real Device SMS, 5 positions). The labels without SMS — API autoreg, Mobile API autoreg, Mobile autoreg — carry no such qualifier in the name. In none of these cases is the number part of the delivery. The other blocks of the name are analysed in the label reference.