更新日志

The API blocks any Single or Browser request whose target URL, follow-redirect chain, or proxy field resolves to a private or reserved IP range. Even if a public target redirects into an internal network, the request stops before it gets there.

The language switcher across the main site, blog, docs, and Updates portal got an overhaul. Each option shows the language's native name plus its name in your current UI language (so 'Deutsch · немски' on the Bulgarian site), with a search box that filters all 13 locales by name, code, or locale id. Each option is now a real link with hreflang, so search engines and AI crawlers can follow every translation, and you can cmd-click to open another language in a new tab. The switcher also lives in the footer of every site.

Auto used to ratchet a host's session TTL downward on every replay failure, even when the failure didn't reflect a real cookie expiry. Sessions kept getting evicted and re-solved while their cookies still worked. The TTL now grows on aged successes and only retreats on real expirations, so a learned session for a Cloudflare-cleared host can carry across several minutes instead of dying after the first 403.

Auto sessions now adapt to what each target needs. Sites without interactive challenges run as portable sessions where cookies ride the proxy pool, so rotation and failover come automatically. Sites that bind their unlock to one exit (interactive Cloudflare being the main one) get pinned with a per-clearance concurrency cap, so a burst of replays can't burn through your unlock.

We tightened proxy redaction in stored request payloads. Before, an internal upstream proxy address could leak into the Activity log preview when the original request was mutated for forwarding. Now any raw proxy URL in a stored payload is replaced with the opaque proxy ID (or with [redacted-proxy] if there's no ID to restore). The visible response was already opaque; this closes the same loop on the request preview.

Every Auto response now carries a meta object (which rung won, whether a challenge was solved, attempt count, total credits) plus the working session (proxy, cookies, userAgent) so you can see what cracked the target and replay it yourself. The session.proxy field is the opaque base36 proxy ID, never a raw address. Set returnSession: false if you don't want the session in the response.

Auto now handles non-interactive Cloudflare challenges (the "Checking your browser" wall some protected sites serve) end-to-end, instead of returning the challenge page as if it were content. Two related cases also got fixed: a transport 200 hiding a challenge interstitial now escalates to a real solve, and a challenge that re-serves the wall after dropping a clearance cookie now reloads and pulls the real content. Marathonbet is the headline site that newly passes; vinted and a few other interstitial-on-200 targets also benefit.

刷新 Playground 时，在您的内容重新出现之前，不再闪现静态状态。新增的 Reset 按钮（需二次确认）可一次性清除所有三个 request 标签页、cookie 以及携带的 proxy。现在，根据您的要求，response 也可以将其 proxy ID 或 User-Agent 携带至下一个 request 中，而不是在后台自动应用。

每个 Single response 现在都包含处理该 request 的 proxy ID，Browser response 也是如此。这对于需要固定使用相同 proxy 的链式调用非常有用。

点击 Dashboard 中的列标题即可进行排序。该功能适用于 Activity、API Keys 和 sessions，在自动刷新后依然保留，按住 Ctrl 键点击（Mac 上为 Cmd 键）即可清除选择。当您需要为表格留出更多空间时，侧边栏还可以折叠为图标栏。

Activity 过去显示原始结果字符串（如 Application_fail），而 Overview 则使用友好的标签（App Fail）和相应的颜色。现在 Activity 使用相同的标签和颜色，因此这两个视图的显示内容保持一致。

已认证的调用现在会返回 X-Foura-Request-Id header。将其记录在您自己的日志中，您就可以将任何 request 与 Activity 中的对应行进行匹配，或者将其提交给支持团队，以便我们准确查询我们这边发生的情况。

在 playground 请求加载时点击新的 Cancel 按钮，我们将干净利落地中止该请求。面板将恢复到空闲状态，并显示“Request canceled”提示，而不是显示令人困惑的网络错误。

现在重检队列的清空时间从数周缩短至数天。我们将挑选每个待测 proxy 的时间从约 2 秒降至约 10 ms，使 pool 在高负载下保持更高的新鲜度。轮换中的失效 IP 更少，每一次 Single 和 Proxy Finder 调用都运行在更健康的资源集上。

在解除昨天的单次运行上限后，每当一大批 proxy 占满队列时，刷新操作仍会陷入停滞。我们现在将每个批次分散到不同的子网中，从而使每次运行都能充分利用并发预算。Proxy Finder 池的周转速度提升了 5-10 倍，过期条目在数小时内即可清除。