Run site-extraction work through a low-cost batch agent

A developer sends large extraction jobs to cheaper batch models instead of their main coding agent to keep spending down.

Done with Claude CodeCodexMeta Muse· Advanced· Nov 2026

What they did
When they need to collect data from a very large set of sites, they create a separate agents-SDK task rather than using their regular coding agent. That task runs on a lower-priced model such as Muse, Deepseek, or GPT-6-luna through a batch API. Routine cloud tasks go to cloud agents, and the dotfiles plus agent context are stored in a GitHub repo so the execution setup can be changed without much friction.
How it went
The example mentions a workload that could cover 5,000 websites, but it does not say what the extraction produced. No timings, costs, accuracy figures, or failure details are provided beyond the reason for the setup: saving money.
Tips
This approach makes the most sense for repetitive jobs where batch processing is acceptable. Keep a small test run in the workflow so you can confirm the script and estimate the cost before expanding it.

Try it yourself with Claude Code

You are helping me automate a bulk extraction job. From [input file or folder], visit [number] websites and collect [data fields] into [output format]. Use a cheap model through a batch API, and start with a small pilot on 10 sites so I can review the sample output and estimated cost. Stop and ask for my approval before launching the full run or doing anything irreversible, and record any failed sites in a separate log.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.