Docs for v2 are being rewritten.

01/Getting started

1. 01Attach an accountIn the console, pick a network and paste a credential — a Discord user token, a Telegram login, an app password. Zenix seals it, then one check resolves the whole account — profile, email and phone where the network exposes them, badges, verification, servers and channels — and caches it, so opening the account again costs no further request. 17 of 20 networks are attachable today; the rest are on the roadmap and cannot be attached yet.
2. 02Or create oneYou do not have to bring an account to use Zenix. Registration is live on Discord, Stoat, Twitch and Kick: Zenix rents a mailbox, registers, solves the captcha, follows the confirmation mail and attaches a number where the network demands one, and the account lands in your console ready to use. X, Mastodon, Bluesky and GitHub are in beta: the flow is built from a capture of the real sign-up, but how far a run gets differs by network, and some stop at a wall that cannot be cleared outside the network's own app. Each network's card on the tool shelf says exactly where its registrar stands — read that before relying on one. Creation draws on the suppliers below — a captcha solver, a mailbox, and a number where one is required — so connect those first.
3. 03Or sign in with a passwordWhere the network has a real login flow — Discord, Steam, Epic Games and GitHub — you can attach an account by signing in with its username and password instead of pasting a token. The session it mints is durable, where a pasted token is something the platform can expire under you. Accounts behind two-factor or device verification cannot be attached this way; sign in once in a browser and paste the cookie instead.
4. 04Browse what the check foundEach account shows its servers; open one for its overview, its channel tree (channels the account cannot see are marked hidden), and — once scraped — its members. Every section shows its own last-checked time.
5. 05Scrape a server's membersFrom a server's Members tab, or the Server members tool, Zenix walks the member-list socket to enumerate members with roles, join dates, presence and boosts, marks the owner, and caches the result onto the server so it only runs once. Large servers return the listable subset Discord exposes, not the full count.
6. 06Send, post and scheduleMessaging is not a separate product: a send is a job like any read. DM one contact or a list of them with a randomised gap between sends, post and like on the networks that have a timeline, and set a recurring sender to fire on a schedule. Each send gets its own run record, so a campaign is auditable per target rather than as one opaque batch.
7. 07ExportScraped member lists and run results export to CSV straight from the page.
8. 08Connect your suppliersFour pages under Resources hold the things a run spends. Proxies is the egress every run goes out through — connect a VaultProxies key to see remaining bandwidth and balance, and get a warning in the bell when either runs low. Solver holds the captcha provider, Email rents the mailboxes a registration confirms through, and Phone rents the numbers a network asks for. Reads and sends need only the proxies; creating accounts needs the rest.

X, Instagram, Reddit, TikTok, Snapchat, Outlook, Steam and Epic Games are in beta: the adapter works, but the surface is still moving and a run can break between deploys. Beta networks are Elite-only for that reason. More networks are on the roadmap — the changelog is the source of truth for what actually works. Stuck on something? Support.