FBFB 助手FB Assistant

使用指南User Guide

从注册到跑起来的每一步，以及每个功能实际是怎么用的。重点标出了那些「做错了不会当场报错、但后果会晚几天才出现」的地方。Every step from signing up to running, and how each feature actually works. The things that don't fail loudly — but whose consequences show up days later — are called out.

01注册与登录

客户端里自助注册，不需要向我们申请账号。

  1. 填用户名、邮箱、密码
  2. 点「发送验证码」，去邮箱收一个 6 位数字
  3. 填回验证码完成注册，注册即登录
验证码收不到？先看垃圾邮件。同一个邮箱有 60 秒冷却， 频繁点发送会被限流；换邮箱也绕不过去（按 IP 另有一道限制）。
一个账号同一时间只能在一处登录。 在第二台电脑登录，第一台会被挤下线并退回登录页。这是刻意的—— 账号数据和 IP 绑定都在本机，两处同时跑会让同一个 FB 账号从两个出口出去。 要换电脑请用账户安全里的导出/导入，不要两边同时开。

02充值与点数

所有消费都用点数结算。充值用 USDT-TRC20（波场链），最低 50 USDT。 充值一次到账多少点、有多少赠送，以客户端下单页面当时显示的为准—— 充得越多，赠送比例越高。

付款金额一分都不能改。 所有人共用同一个收款地址，我们靠金额的小数尾数认出这笔钱是谁付的—— 订单会给你一个像 50.37 这样的金额，.37 就是你这笔订单的身份。 付成 50.00 或 50.38 都不会到账，而链上转账不可撤销。 请直接复制订单里的金额，不要手打、不要凑整。
只支持 TRC20 这一条链。 用 ERC20（以太坊）、BEP20（币安链）转过来，钱不会到账也无法找回—— 那是另一条链上的另一个地址。交易所提币时把网络选成 TRC20。

二维码和金额 30 分钟有效，超时请重新下单拿新金额，不要再往旧金额上付。 另有 10 分钟宽限：二维码刚过期但转账在这段时间内上链，仍会被认出来。

到账通常 1–3 分钟。后台在轮询链上记录，不需要一直开着客户端， 关了软件也照样入账。

兑换码：给自己的员工充值

如果你有员工各自用独立账号，不必让每个人都去充 USDT—— 你充一次，然后把自己的点数兑成兑换码发给他们。

  1. 在客户端里选一个面额，生成一张兑换码
  2. 把码发给员工
  3. 员工在自己账号里输入这张码，点数直接进他的余额
面额你实际被扣员工到账
50,000 点51,000 点50,000 点
100,000 点101,000 点100,000 点
200,000 点201,000 点200,000 点

每张码收 1,000 点手续费，从你的余额里另扣——所以码的面值就是员工拿到的数， 不用再去想「是不是已经被扣过手续费了」。

为什么值得这么用：员工各自独立账号， 每个人的 FB 账号、IP、数据互不相通——某个员工的号出了问题， 不会牵连到其他人。而点数由你统一充、按需分发，花销仍然在你手里。
兑换码一次性、用了就作废，请当现金看管。 发出去之前确认收件人无误，谁先输入就归谁。

03固定 IP

每个 FB 账号会独占一条固定住宅 IP，不与任何其他账号共用。 新建账号时选一个出口国家，客户端会自动为它领一条。

按「30 天服务周期」计费，不是按某一条 IP

你买的是这个账号 30 天的固定 IP 服务。期间那条 IP 如果坏了、 或者被上游供应商收回，我们会免费换一条， 到期日不变、不重新计算、不补差价。

举例：第 12 天那条 IP 被供应商收回，系统自动换上新的一条—— 你的服务期仍然在原来的第 30 天结束，不会因为换了 IP 就重新算 30 天。

价格随国家不同。IP 是我们从供应商进的货，各国进价差好几倍， 所以美国和日本不是一个价。选国家时客户端会显示具体多少点。

到期与续费

到期时系统自动尝试扣下一期：

  • 余额够 → 自动续期，IP 不变，你完全不会察觉
  • 余额不足 → 收回该账号的 IP
被收回之后，那个 FB 账号会直接断网—— 而不是改用你本机的网络。这是刻意的保护： 用你的真实住宅 IP 去登一个一直在用海外 IP 的账号，等于当场自曝。 充值之后在客户端点一下就能续上，而且拿回的是同一套服务，不用重新建号。

IP 出问题了怎么办

先别急着换。客户端会先自己判断是你本机网络抖动还是那条 IP 真的坏了—— 前者等一会儿会自己恢复，这时候换 IP 反而有害。

确认是 IP 坏了，会提示你手动换一条：免费，每个账号每天一次。

为什么不自动帮你换？ 换 IP 本身就是 Facebook 眼里的异常信号。该不该换、什么时候换， 应该由你决定，而不是系统替你决定。

如果提示「暂无可用地址，正在补货」，是那个国家的库存暂时空了。 客户端会每 30 分钟自动重试，补上了会自己恢复，不用一直盯着。 如果提示「线路供应商正在异常」，是上游机房大面积故障， 这时换任何 IP 都一样连不上，系统会暂停该账号并等待恢复， 不会白白消耗你的免费更换次数。

04账号管理

每个 FB 账号在客户端里是一个完全独立的环境：独立的浏览器指纹、 独立的 Cookie 和本地存储、独立的固定 IP。账号之间不共享任何东西。

首次登录 Facebook 必须由你本人完成。 账号密码、验证码、安全检查这些都得人来过——我们不接触你的 FB 密码， 也不代你过验证。首次登录是账号最敏感的一次操作， 由本人在干净的 IP 上完成，之后才适合挂机。

05账户安全

换电脑：整机迁移

在旧机器上导出（用你的登录密码加密成一个文件），在新机器上导入。 迁移过去的不只是账号列表：

  • FB 账号不用重新登录。登录状态一起加密打包过去， 新电脑打开直接就是登录好的，不用再输 FB 的账号密码
  • 设备指纹连续。这个号在新电脑上，对 Facebook 仍然表现为 原来那台机器——不会因为「换了设备」触发风控
  • 固定 IP 的绑定关系也跟着走，账号还是用原来那条出口
整机迁移是「搬家」，不是「复制」。 导出成功后，旧电脑上的账号会自动清空并登出——这是故意的： 同一个号同时在两台机器上跑，对 Facebook 来说是明显的异常。 固定 IP 不会被回收，它跟着账号去新电脑。
唯一需要你做的一步：在新电脑上用你自己的账号密码 登录一次本客户端。这是登录我们的软件，不是登录 Facebook—— FB 账号本身不需要重登。
导出前务必确认密码输对了。 导出成功后旧机器上的数据会被清空。密码打错一个字符， 备份文件就用错误的密钥加密了，到新机器上再也打不开，且无法找回。 客户端在这一步会先让服务端核对一次密码，请不要跳过。

把账号转给别人

除了整机迁移，也可以把单个 FB 账号连同它的固定 IP 转给另一个客户。 服务端这边走的是交接码：你发一张码给对方，对方认领之后， 那条 IP 的归属才真正转到他名下。

  • 对方不用重新登录 FB。登录状态跟着账号一起过去， 对方认领后打开就是登录好的
  • 设备指纹跟着走。这个号在对方电脑上，对 Facebook 仍然表现为 原来那台机器，不会因为易手而触发换设备风控
  • 那条固定 IP 的归属一并转移，账号还是用原来的出口
转让是全部成功或全部不发生。 交接过程中那条地址会被挂起——你退不掉、别人也领不走， 避免出现「你以为给出去了、对方却没收到」的中间状态。 码没被认领之前可以撤回。

谷歌验证器（两步验证）

可以给自己的账号绑定谷歌验证器，绑定后登录需要额外输入 6 位动态码。 建议绑定——你的余额和所有 FB 账号数据都在这个账号下面。

改密码

改密码会让所有已登录的会话立即失效，包括你自己正在用的那台。 这是有意的：怀疑账号被盗时，改密码就是最直接的止损手段。

06目标画像

画像是你告诉系统「我想加什么样的人」。可以存多份，随时切换。

字段怎么填
画像名称自己认得出就行，比如「日本 30+ 女性」
人种必选：亚裔 / 阿拉伯裔 / 印度裔 / 欧美裔 / 非裔
性别不限 / 男 / 女
年龄区间18–100 之间的一段
关键词加分关键词 + 百分比（−100% ~ +100%）。 比如「旅行 +20%」表示对方内容里出现旅行相关信号时提分
画像不是硬过滤，是给 AI 的判断依据。 人种、性别、年龄用在头像初筛那一步；关键词加分用在主页复核那一步。 它们被拼进给 AI 的提示里，由 AI 综合判断，而不是一条条硬性排除。

加好友：照片与文字分析

这是这套系统最花力气的地方。加好友之前，系统会先替你把人看一遍—— 分两段，不合格的在第一段就被挡掉，不浪费后面的时间和额度。

第一段：头像初筛（便宜、快、挡掉大多数）

只看对方的头像和名字，让 AI 判断三件事：

  • 是不是清晰的真人照片（挡掉风景图、卡通、logo、模糊图）
  • 表观的人种、性别、年龄是否符合你的画像

输出一个 0~1 的分数，达到阈值（默认 0.8）才进入下一段。

为什么要分两段：点开一个主页、采集内容、再让 AI 读完， 成本远高于看一眼头像。先用便宜的一步筛掉大多数，剩下的才值得细看。

第二段：主页复核（看内容，判断经济水平与形象）

进到对方主页，采集这些交给 AI 一起看：

采集什么数量上限用来判断
简介资料4,000 字以内职业、所在地、生活状态等文字信号
帖子文字约 8 条，每条 800 字以内日常内容、关键词是否命中你的画像
帖子配图最多 6 张车、房、旅行、衣着——经济水平的视觉信号
本人照片最多 4 张形象气质

一个人一次最多约 10 张图加上几千字文本，一起送给 AI。AI 给回：

  • 经济分 0~1，以及一个档位：中产以上 / 中产 / 低于中产 / 无法判断
  • 形象分 0~1
  • 命中了哪些关键词、依据了哪些信号
  • 一句中文理由

最终分的算法是：

最终分 = 经济分 × (1 + 关键词加成) × (1 + 形象分 × 形象上限)

达到经济阈值（默认 0.6）才会发好友请求。没通过的人进7 天跳过缓存， 这段时间内不会再被重复筛一遍。

关键词和形象是在经济分基础上「放大」，不会凭空把人抬过线。 看不出经济水平的人（资料为空、主页锁定、几乎没有帖子）会拿到一个偏低的中性分—— 这是有意的：「看不出来」和「确实水平低」是两回事，不该给同一个分。 默认设置下，这样的人就算形象拉满、关键词全中，也到不了通过线， 所以不会因为「照片好看」就被加进来。
而 AI 明确判断为经济水平低的人，分数接近 0——那种情况下形象和关键词乘上去也还是接近 0， 形象再好也不起作用。
财力和形象是 AI 的概率判断，不是事实核查。 它读的是公开内容里的信号，会有误判。请把它当作辅助筛选， 用来把明显不符的人挡在外面、节省你的时间，而不是当成对一个人的准确画像。

通过筛选之后，系统先随机给对方点赞 3~5 条帖子，再发好友请求—— 上来就加人不像真人的行为。

每个人的评分和理由都会写进行动日志， 包括为什么通过、为什么跳过。想知道「为什么这个人没被加」，去日志里查那一条。
发好友请求不带附言。 系统只点「添加好友」按钮，不发验证消息、也没有私信功能。

07玩法模版

模版是一整套任务配置——决定这个账号这次要怎么跑。分两类：

类型它做什么
加人模版打开人名单 → 头像初筛 → 主页复核 → 点赞 3~5 条 → 发好友请求 → 检查有没有被风控 → 继续，直到当天上限
浏览模版刷短视频、进帖子看内容，按概率点赞或回复。用来养号
「模版」不是打招呼话术。 这里配的是玩法参数，不是可编辑的消息文本——系统不发私信、不带验证附言， 也不支持 {名字} 这类变量替换。

模版可以存任意多个、可以复制、系统自带几个预设。 在工作台顶部下拉里手动选一个当前生效——不会自动轮换。

加人途径（加人模版里可多选）

  • 可能认识的人推荐
  • 按城市搜索
  • 姓氏 + 城市
  • 职业 + 城市
  • 种子好友的好友
先养号，再加人。 加好友是最容易触发风控的动作（触发后有 24 小时冷却熔断），浏览则不受限制。 新号建议先用浏览模版跑一段时间，等账号成熟再开始加人。 这是运营建议，不是系统强制。

08行动日志

系统做的每一个动作都记在这里，细到单次点赞。

  • 任务开始 / 结束、浏览、刷短视频、进帖、点赞、回复
  • 发出好友请求（加了谁）、候选人被跳过或移除（带 AI 评分和理由）
  • 撞上验证码或安全检查、加人冷却触发

每条带时间、账号、动作、结果，以及结构化的详情（评分、阈值、截图路径等）。 可按账号 / 动作 / 级别 / 关键词筛选。

保留最近 5,000 条，按条数滚动覆盖（不是按天）。 删除某个账号时，它的日志一并删除。目前不支持导出。

每日统计（浏览、点赞、回复、加人四项）就是从日志里算出来的—— 达到当天上限会自动停下收尾。

日志最有用的时候是「为什么没效果」。 加人数量上不去，去日志里看是卡在头像初筛、还是卡在主页复核、 还是根本没找到候选人——这三种情况该调的参数完全不同。

09参数设置

这些是全局设置，对所有账号生效。 账号级别只能单独设备注名和代理，自动化参数是所有账号共用一套。

运行与性能

参数默认调错会怎样
同时运行几个账号3（上限 5） 调到上限会明显吃内存和 CPU，实测会出现大量偶发超时
空闲自动休眠开 关掉的话，20 个账号大约占 6.6 GB 内存
空闲几分钟后休眠5 分钟 设太短会反复卸载/重载页面，每次唤醒约 19 秒，反而更慢
模拟人工延迟2~6 秒 设太小节奏像机器人，风控风险上升
可管理账号总数上限 20，同时运行上限 5。 「管着 20 个」和「同时跑 20 个」是两回事。

排队：想跑的号多于并发上限时

你可以一次勾选很多个号开始挂机，不用自己分批。真正同时在跑的不会超过 「同时运行几个账号」这个设置（默认 3、上限 5），多出来的号自动进队列。

  • 排队中的号状态显示「排队中」，并标出它排第几位。 前面的号跑完会自动递补开跑，不用你盯着手动开下一个
  • 排队中的号随时可以停掉，和运行中的号一样操作
  • 没有排队超时，会一直等到有空位为止
  • 排队中的号不启动自动化，它什么都不做
排队期间不扣任何费用。 计费从这个号真正轮到它开始跑的那一刻起算，而不是你点下开始的那一刻—— 排在队里的号什么都没做，不按分钟计费，也不会产生任何 AI 调用。 所以一次多勾几个号排着，不会因为「等得久」而多花钱。

AI 筛选

参数默认调错会怎样
头像初筛阈值0.8 调太高几乎没人能通过，加人效率极低；太低会把大量不符画像的人放进主页复核， 白烧 AI 额度
经济复核阈值0.6 同上。建议「头像严、经济松」——头像那步便宜，多挡一些划算。
但别调得太低：那些「看不出经济水平」的人拿的是偏低的中性分， 默认 0.6 正好把他们挡在外面；阈值一低，这层保护就没了
形象加分上限30% 设太高，会让「颜值高但经济一般」的人更容易通过。设 0 = 完全不看形象
单轮每种途径最多筛几人30（0 = 不限） 设太大或设 0，会在一个出不了货的途径上无限筛下去，白烧 AI 额度
进主页后等待秒数3 秒 设太小会读到还没渲染完的空页面，白白浪费一次 AI 调用

每日上限（安全刹车）

动作默认上限 / 天
浏览100
点赞20
回复10
加好友10
加好友默认 10 个/天，但这是给「已经养稳」的号用的数。 新号请自己手动调到 2 左右，跑一段时间、账号稳定之后再放回 10。 新号一上来就按 10 冲，是最容易触发风控的做法之一—— 账号被封的代价远大于慢几天。
软件不会替你判断账号稳不稳。10 对新号也是从第一天就生效的， 没有「识别到是新号就自动放慢」这回事——前期调低要你自己动手。
「默认值」只对没动过这项设置的人生效。 如果你以前改过每日上限，客户端会一直用你自己存的那个数—— 升级不会把它改回默认。所以你打开设置看到的数和这里写的不一样， 不是出错，是你之前设过。想用新默认，手动填一次就行。
这些上限是按账号算的，而且不分途径。 比如加好友这条：一个账号无论走哪条途径（可能认识的人、按城市搜索、 姓氏或职业加城市、种子好友的好友），加出去的请求都记在同一个计数器上—— 不是每条途径各给一份额度。多开几条途径只会让候选人来源更广， 不会让这个号今天能加更多人。

其他

参数默认说明
互动语言English设成和目标人群不符的语言，通过率会降
挂机前检查代理连通开 挂机前先探一次代理通不通。关掉只是跳过这次探测，不会让流量绕过代理—— 代理是绑在账号的浏览器会话上的，和这个开关无关。
关掉的代价是：代理其实不通时它不会拦你，你可能对着一条连不上的 IP 空跑、白等。建议保持开启，但它是省事，不是防漏

10几件容易误解的事

帖子回复是 AI 根据帖子内容生成的。 它会读这条帖子，然后写一句话——只表达感受、共情或祝福， 不发表观点、不提问、也不推销。风格上是「路过点个头」，不是聊起来。
回复始终用你在设置里选的「互动语言」，不管帖子本身是什么语言—— 所以这个设置选错，回复出去的语言就会和对方对不上。
AI 筛选目前不额外收费。 任务按分钟计费（加人和浏览费率不同），筛选过程中的 AI 调用不单独计价。

01Signing up

You register yourself inside the client — there's no application to send us.

  1. Enter a username, email and password
  2. Hit "Send code" and collect the 6 digits from your inbox
  3. Type the code back in — registering signs you in
Code didn't arrive? Check spam first. There's a 60-second cooldown per email address, and hammering the button gets you rate-limited; switching email doesn't get around it either (there's a separate per-IP limit).
One account can only be signed in one place at a time. Sign in on a second computer and the first is kicked back to the login screen. That's deliberate — account data and IP bindings live on the machine, and running two at once would put the same Facebook account behind two different exits. To change computers use export/import under Account security; don't run both at the same time.

02Credits

Everything is billed in credits. Top up with USDT-TRC20 (TRON), minimum 50 USDT. How many credits a top-up gives and what bonus applies is whatever the client's order page shows at the time — the more you add, the higher the bonus rate.

The payment amount can't be changed, not by a cent. Everyone pays into the same address, and we identify your payment by the decimals in the amount — your order shows something like 50.37, and that .37 is its fingerprint. Paying 50.00 or 50.38 means it won't credit, and on-chain transfers can't be reversed. Copy the amount from the order — don't type it, don't round it.
TRC20 only. Send via ERC20 (Ethereum) or BEP20 (BNB Chain) and the money neither arrives nor can be recovered — that's a different address on a different chain. Set the network to TRC20 when withdrawing from an exchange.

The QR code and amount are good for 30 minutes. After that, create a new order for a fresh amount and don't pay against the old one. There's a 10-minute grace period: if the code has just expired but your transfer lands within it, it's still recognised.

Credits usually land in 1–3 minutes. Our servers poll the chain, so you don't need to keep the client open — close it and the credit still lands.

Redeem codes: topping up your staff

If your staff each use their own account, they don't each need to buy USDT — you top up once, then turn your credits into redeem codes and hand them out.

  1. Pick a denomination in the client and generate a code
  2. Send the code to your employee
  3. They enter it in their own account and the credits land in their balance
DenominationDeducted from youThey receive
50,000 credits51,000 credits50,000 credits
100,000 credits101,000 credits100,000 credits
200,000 credits201,000 credits200,000 credits

Each code costs 1,000 credits in fees, taken separately from your balance — so the face value is exactly what your employee gets, with no "has the fee already come out of this?" arithmetic.

Why this is worth doing: separate accounts mean each person's Facebook accounts, IPs and data are unconnected — if one employee's account runs into trouble it doesn't reach the others. Meanwhile you fund everything centrally and hand out credits as needed, so spending stays under your control.
Codes are single-use and burn on redemption — treat them like cash. Check the recipient before sending; whoever enters it first keeps it.

03Fixed IP

Every Facebook account gets a fixed residential IP of its own, shared with no other account. Pick an exit country when you create the account and the client claims one for it automatically.

Billed per 30-day service period, not per IP

What you buy is 30 days of fixed-IP service for that account. If the IP breaks during the period, or the upstream supplier takes it back, we replace it free and the end date doesn't move, doesn't restart, and there's nothing extra to pay.

For example: on day 12 the supplier reclaims that IP and the system swaps in a new one — your service still ends on the original day 30. Changing IP does not restart the 30 days.

Prices vary by country. IPs are stock we buy from suppliers and wholesale prices differ several-fold between countries, so the US and Japan aren't the same price. The client shows the exact credit cost when you pick the country.

Expiry and renewal

At the end of a period the system tries to charge the next one:

  • Enough balance → renewed automatically, same IP, completely invisible to you
  • Not enough → that account's IP is reclaimed
Once reclaimed, that Facebook account simply loses network access — it does not switch to your own connection. That's deliberate protection: signing into an account that has always used an overseas IP from your real home address exposes it on the spot. Top up, click once in the client, and it's back — the same service, with no need to set the account up again.

When an IP has problems

Don't rush to replace it. The client first works out whether your own connection hiccuped or that IP is genuinely dead — the former recovers by itself, and changing IP at that moment does harm rather than good.

Once a dead IP is confirmed, you'll be prompted to swap it manually: free, once per account per day.

Why don't we swap it for you? Changing IP is itself an anomaly in Facebook's eyes. Whether and when to do it should be your call, not something the system decides on your behalf.

If you see "no address available, restocking", that country is temporarily out of stock. The client retries every 30 minutes and recovers on its own once stock lands — you don't have to watch it. If you see "the line supplier is having problems", there's a wide outage upstream; swapping to any other IP would fail the same way, so the system pauses that account and waits, and your free replacements aren't wasted.

04Managing accounts

Each Facebook account is a completely separate environment in the client: its own browser fingerprint, its own cookies and local storage, its own fixed IP. Accounts share nothing.

The first Facebook sign-in must be done by you. Passwords, verification codes and security checks all need a person — we never touch your Facebook password and don't complete verification for you. The first sign-in is the most sensitive moment in an account's life; done by the real person on a clean IP, it's ready for automation afterwards.

05Account security

Changing computers: moving everything

Export on the old machine (encrypted into a file with your login password) and import on the new one. What moves is more than a list of accounts:

  • Your Facebook accounts stay signed in. The login state is packed and encrypted along with everything else, so the new computer opens straight into signed-in accounts — no re-entering Facebook passwords
  • Device fingerprints carry over. On the new computer the account still looks to Facebook like the original machine — no "new device" risk trigger
  • The fixed-IP binding travels too; the account keeps the same exit
This is a move, not a copy. Once the export succeeds, the accounts on the old computer are cleared and signed out — deliberately: the same account running on two machines at once is an obvious anomaly to Facebook. The fixed IP isn't reclaimed; it follows the account to the new computer.
The one thing you have to do: sign into this client once on the new computer with your own username and password. That's signing into our software, not into Facebook — your Facebook accounts don't need to sign in again.
Make absolutely sure the password is right before exporting. The old machine's data is cleared once the export succeeds. One wrong character and the backup is encrypted with the wrong key — it will never open on the new machine, and it can't be recovered. The client checks the password with our servers at this step; please don't skip it.

Handing an account to someone else

Besides moving everything, you can transfer a single Facebook account together with its fixed IP to another customer. On our side this runs through a handover code: you send a code, and the IP's ownership only moves once they claim it.

  • They don't have to sign into Facebook again. The login state travels with the account, so it opens already signed in once claimed
  • The device fingerprint travels too. On their computer the account still looks to Facebook like the original machine — changing hands doesn't trigger a new-device check
  • Ownership of the fixed IP moves with it; the account keeps the same exit
A transfer either completes or never happened. While it's in flight the address is held — you can't release it and nobody else can claim it, so you never get the middle state where you think it's gone but they never received it. Until the code is claimed you can cancel it.

Authenticator (two-factor)

You can attach Google Authenticator to your account; after that, signing in also needs a 6-digit code. We recommend it — your balance and all your Facebook account data sit under this one account.

Changing your password

Changing the password invalidates every signed-in session immediately, including the one you're using. That's intentional: if you suspect your account is compromised, changing the password is the most direct way to stop the bleeding.

06Target profile

A profile is how you tell the system "this is the kind of person I want to add". You can save several and switch between them.

FieldHow to fill it
Profile nameAnything you'll recognise, e.g. "Japan, women 30+"
EthnicityRequired: Asian / Arab / Indian / Western / African
GenderAny / Male / Female
Age rangeA span between 18 and 100
Keyword weightingKeyword + percentage (−100% to +100%). "Travel +20%" raises the score when travel-related signals appear in their content
A profile isn't a hard filter — it's context for the AI. Ethnicity, gender and age are used at the avatar screening step; keyword weighting at the profile review step. They're folded into the prompt and weighed together, rather than excluding people one rule at a time.

Adding friends: photo and text analysis

This is where the system does its heaviest work. Before adding anyone, it looks the person over for you — in two passes, so the ones who don't fit are stopped in the first pass and don't cost you time or quota in the second.

Pass one: avatar screening (cheap, fast, stops most)

It looks only at the profile photo and name, and judges:

  • Whether it's a clear photo of a real person (screening out scenery, cartoons, logos and blurry images)
  • Whether apparent ethnicity, gender and age match your profile

It returns a score from 0 to 1; only those at or above the threshold (default 0.8) go through to pass two.

Why two passes: opening a profile, collecting content and having the AI read all of it costs far more than glancing at an avatar. The cheap step removes most candidates, and only what's left is worth a close look.

Pass two: profile review (reads content, rates spending power and presentation)

It opens the profile and collects the following for the AI to read together:

What's collectedLimitWhat it's read for
Bio / aboutUp to 4,000 charactersOccupation, location, life stage and other written signals
Post textAbout 8 posts, up to 800 characters eachEveryday content, and whether keywords from your profile appear
Post photosUp to 6Cars, homes, travel, clothing — visual signals of spending power
Photos of themUp to 4Presentation

That's roughly 10 images plus a few thousand characters of text per person, sent to the AI in one go. It returns:

  • Spending-power score 0–1, plus a band: above middle class / middle class / below middle class / can't tell
  • Presentation score 0–1
  • Which keywords matched and what signals it relied on
  • A one-line reason

The final score is:

final = spending × (1 + keyword bonus) × (1 + presentation × presentation cap)

Only scores at or above the spending threshold (default 0.6) get a friend request. People who don't pass go into a 7-day skip cache and won't be screened again during that time.

Keywords and presentation amplify the spending score — they can't lift someone over the line on their own. Someone whose spending power can't be read (empty profile, locked page, almost no posts) gets a deliberately low neutral score. That's on purpose: "can't tell" and "clearly low" are different things and shouldn't get the same score. With default settings such a person won't reach the threshold even with maximum presentation and every keyword matching — so nobody gets added just for being photogenic.
Someone the AI judges to be genuinely low scores close to 0 — and multiplying near-zero by presentation and keywords still leaves near-zero, so good looks change nothing.
Wealth and presentation are probabilistic judgements, not fact checks. The AI reads signals in public content and it will sometimes be wrong. Treat it as assisted filtering — a way to keep the obviously unsuitable out and save your time, not as an accurate portrait of a person.

Once someone passes, the system likes 3–5 of their posts at random first, then sends the friend request — going straight to "add" isn't how a person behaves.

Every score and reason is written to the activity log, both for people who passed and people who were skipped. If you want to know why someone wasn't added, find their entry there.
Friend requests carry no note. The system only clicks "Add friend" — it sends no verification message, and there is no direct-message feature.

07Templates

A template is a whole task configuration — how this account runs this time. There are two kinds:

TypeWhat it does
Add-friend templateOpen a candidate list → avatar screening → profile review → like 3–5 posts → send friend request → check for a risk block → carry on until the daily cap
Browse templateWatch short videos, open posts and read them, liking or replying by probability. Used to warm an account up
"Template" doesn't mean an opening script. What you configure here are behaviour parameters, not editable message text — the system sends no direct messages, adds no note to requests, and has no {name}-style variable substitution.

You can save as many templates as you like, duplicate them, and there are a few presets. Pick the active one by hand from the dropdown at the top of the workspace — it doesn't rotate automatically.

Candidate sources (choose several in an add-friend template)

  • People You May Know
  • Search by city
  • Surname + city
  • Occupation + city
  • Friends of a seed friend
Warm the account up before adding anyone. Sending friend requests is the action most likely to trip a risk block (which brings a 24-hour cooldown), while browsing isn't limited. For a new account, run a browse template for a while first and start adding once it has matured. That's operational advice, not something the system enforces.

08Activity log

Every action the system takes is recorded here, down to a single like.

  • Task start / end, browsing, short videos, opening posts, likes, replies
  • Friend requests sent (and to whom), candidates skipped or removed (with the AI score and reason)
  • Hitting a captcha or security check, add-friend cooldowns triggered

Each entry carries a timestamp, account, action and result, plus structured detail (scores, thresholds, screenshot paths). You can filter by account / action / level / keyword.

The most recent 5,000 entries are kept, rolling by count rather than by date. Deleting an account deletes its log with it. There is currently no export.

The daily counters (browsing, likes, replies, friend requests) are computed from this log — hitting the day's cap stops the task and winds it down.

The log earns its keep when nothing seems to be working. If friend counts aren't going up, check whether it's stalling at avatar screening, at profile review, or not finding candidates at all — those three call for completely different adjustments.

09Settings

These are global and apply to every account. Per-account you can only set a display name and a proxy; the automation parameters are shared by all accounts.

Running and performance

SettingDefaultWhat goes wrong if you get it wrong
Accounts running at once3 (max 5) At the maximum, memory and CPU use are noticeable and we've measured a lot of intermittent timeouts
Sleep when idleOn Turn it off and 20 accounts take roughly 6.6 GB of memory
Minutes before sleeping5 minutes Too short and pages unload and reload constantly — each wake-up takes about 19 seconds, so it ends up slower
Human-like delay2–6 seconds Too small and the pacing looks robotic, raising the risk of a block
Up to 20 accounts managed, up to 5 running at once. "Managing 20" and "running 20" are different things.

Queueing: when you start more accounts than the concurrency limit

You can select many accounts at once — no need to batch them yourself. The number actually running never exceeds the "accounts running at once" setting (default 3, max 5); the rest queue automatically.

  • A queued account shows as Queued with its position. When one ahead finishes, the next starts on its own — you don't have to watch and launch the next by hand
  • Queued accounts can be stopped at any time, same as running ones
  • There's no queue timeout; it waits until a slot frees up
  • A queued account isn't running automation — it's doing nothing
Queueing costs nothing. Billing starts the moment an account actually begins running, not when you press start — a queued account has done nothing, so there's no per-minute charge and no AI calls. Queueing several accounts at once never costs more just because they waited longer.

AI screening

SettingDefaultWhat goes wrong if you get it wrong
Avatar screening threshold0.8 Too high and almost nobody passes, so you add hardly anyone; too low and crowds of off-profile people reach profile review, burning AI quota for nothing
Spending review threshold0.6 Same idea. We suggest "strict on avatars, relaxed on spending" — the avatar step is cheap, so filtering more there pays off.
But don't set it too low: people whose spending power can't be read get a deliberately low neutral score, and 0.6 is exactly what keeps them out. Drop the threshold and that protection goes with it
Presentation bonus cap30% Set it high and "good-looking but average means" passes more easily. Set 0 to ignore presentation entirely
Max screened per source per round30 (0 = unlimited) Too large, or 0, and it will screen forever on a source that isn't producing — burning AI quota
Wait after opening a profile3 seconds Too short and it reads a page that hasn't finished rendering, wasting an AI call

Daily caps (the safety brake)

ActionDefault cap / day
Browsing100
Likes20
Replies10
Friend requests10
Friend requests default to 10/day, but that figure is for an account that's already settled. On a new account, set it down to about 2 yourself, run it for a while, and put it back to 10 once the account is stable. Pushing 10 from day one on a new account is one of the surest ways to trigger a block — and losing the account costs far more than a few slower days.
The software will not judge for you whether an account is settled. The 10 applies from day one on a new account too; there's no "detects a new account and slows down" behaviour — lowering it early is something you do by hand.
"Defaults" only apply to people who never changed the setting. If you've edited the daily caps before, the client keeps using your saved number — upgrading doesn't reset it. So if the number in settings differs from what's written here, nothing is broken; it's the value you set. To use the new default, type it in once.
These caps are per account, and they don't split by source. Take friend requests: whichever sources an account uses (People You May Know, city search, surname or occupation plus city, friends of a seed friend), every request lands on the same counter — each source doesn't get its own allowance. Adding more sources only widens where candidates come from; it doesn't let that account add more people today.

10Common misreadings

Post replies are AI-written, based on the post itself. It reads the post and writes one line — expressing a feeling, empathy or good wishes only. No opinions, no questions, no selling. The register is "nodding as you pass", not starting a conversation.
Replies always use the "interaction language" you chose in settings, whatever language the post is in — so getting that setting wrong means replying in a language the other person doesn't use.
AI screening costs nothing extra right now. Tasks bill by the minute (adding and browsing have different rates); the AI calls made during screening aren't priced separately.