Solution skill
ZenRows mode=auto bills only for what succeeds - stop pre-enabling js_render and premium_proxy everywhere
Complete solution
ZenRows mode=auto bills only for what succeeds - stop pre-enabling js_render and premium_proxy everywhere. Their adaptive mode (mode=auto) escalates to rendering and residential proxies only when the simple fetch fails - and you are billed only for the configuration that actually succeeds. Use when hitting this exact issue. Not for unrelated errors or different features.
TL;DR
Their adaptive mode (mode=auto) escalates to rendering and residential proxies only when the simple fetch fails - and you are billed only for the configuration that actually succeeds. Stop pre-enabling jsrender and premiumproxy on every ZenRows request.
Fix
Their adaptive mode (mode=auto) escalates to rendering and residential proxies only when the simple fetch fails - and you are billed only for the configuration that actually succeeds. Expected: You get the expected result; the problem is gone.
When to use
- You are dealing with this situation.
- The symptom matches: ZenRows mode=auto bills only for what succeeds - stop pre-enabling jsrender and premiumproxy everywhere.
When NOT to use
- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.
Compatibility
Reported per the linked source.
Variant phrasings
ZenRows mode=auto bills only for what succeeds - stop pre-enabling jsrender and premiumproxy everywhere
Why it happens
ZenRows' own agent skill (zenrows/cli SKILL.md): prefer the cheapest reliable primitive and start with Adaptive Stealth Mode (mode=auto) - ZenRows escalates to JS rendering and premium proxies only when needed, and you are billed only for the configuration that succeeds. Their rule: escalate only with evidence - if a fetch fails, read the trace (zenrows trace explain [run-id]) before adding --js-render or --premium-proxy. Manually pre-enabling jsrender (5 credits) and premiumproxy (10 credits) on every request burns both on pages the adaptive mode would have fetched for 1 credit.
Edge cases
- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.
Evidence
Source: ZenRows' own agent skill (zenrows/cli SKILL.md): prefer the cheapest reliable primitive and start with Adaptive Stealth Mode (mode=auto) - ZenRows escalates to JS rendering and premium proxies only when needed, and you are billed only for the configuration that succeeds. Their rule: escalate only with evidence - if a fetch fails, read the trace (zenrows trace explain [run-id]) before adding --js-render or --premium-proxy. Manually pre-enabling jsrender (5 credits) and premiumproxy (10 credits) on every request burns both on pages the adaptive mode would have fetched for 1 credit.
Verified resolution: Stop pre-enabling jsrender and premiumproxy on every ZenRows request. Their adaptive mode (mode=auto) escalates to rendering and residential proxies only when the simple fetch fails - and you are billed only for the configuration that actually succeeds. The documented workflow: try the cheap fetch first, and only escalate when the trace explains why it failed. Pre-enabling the expensive flags on everything is the credit-burn anti-pattern their own skill guide warns against.
Source URL: https://github.com/zenrows/cli/blob/HEAD/skills/zenrows/SKILL.md
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_NUmOa1uFB_sbWGnznZdz0A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">ZenRows mode=auto bills only for what succeeds - stop pre-enabling js_render and premium_proxy everywhere <span>— Vectle</span></a>