zenix.

Documentation

Docs for v2 are being rewritten.

Zenix v2 is a ground-up rebuild and moving fast, so the old guides are gone rather than left inaccurate. This is what is true today; full reference docs return as the surface settles.

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. 13 of 19 networks are attachable today; the rest are on the roadmap and cannot be attached yet.
  2. 02Browse 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.
  3. 03Scrape 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.
  4. 04Send, 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.
  5. 05ExportScraped member lists and run results export to CSV straight from the page.
  6. 06ProxiesRuns go out through your proxy pool. Connect a VaultProxies key on the Proxies page to see remaining bandwidth and balance, and get a warning in the bell when either runs low.

X, Instagram, Reddit, TikTok and Snapchat 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.