Skip to content
VZU
VZU OS · Agent

Agent 12 of 12

HUNTER.

Resilient web scraper.

Hunter is the VZU Scrape agent. Resilient web scraper. Headless browsers, proxy rotation, anti-bot handling, retry logic, scheduled runs. The agent that gets the data.

The role

What HUNTER does

HUNTER is the dedicated agent behind VZU Scrape. It runs every time the operator briefs the vzu scrape capability. It owns the goal, the toolset, the memory, the audit trail.

The goal

What HUNTER is trying to achieve

"Scrape the target sites reliably, on schedule, into the operator's data store. Respect robots.txt, terms of service, and rate limits."

The capability

What it powers

HUNTER powers the VZU Scrape capability in the VZU family.

Visit scrape.vzu.ca →

The toolset

5 MCP actions HUNTER can call.

Every action is exposed as an MCP server (Model Context Protocol). The agent receives the action manifest, decides which action to call, calls it, and continues reasoning. The audit trail records every call.

  • mcp.scrape.run

    Run the scraper

  • mcp.proxy.rotate

    Rotate through proxy pool

  • mcp.robots.check

    Check robots.txt

  • mcp.data.deliver

    Deliver to API / CSV / DB

  • mcp.schedule.cron

    Schedule the runs

The memory schema

What HUNTER remembers between calls.

  • The target sites
  • The proxy pool
  • The schedule
  • The delivery config

The brief

A real demo brief.

"Scrape the Bayut property listings daily. 50,000+ listings. Photos, prices, locations. CSV output to S3."

Below is HUNTER's actual execution trace for this brief — every step, every MCP call, every observation, every audit trail entry.

The execution trace

What HUNTER did.

hunter@vzu-os — trace.log
  1. 01 hunter > read brief
  2. 02 hunter > thinking: bayut scraper. 50k+ listings. daily. 2 weeks.
  3. 03 hunter > mcp.robots.check > allowed paths: /properties/*, /agents/*
  4. 04 hunter > mcp.proxy.rotate > 1,200 residential proxies
  5. 05 hunter > mcp.scrape.run > playwright + stealth, 5s/listing
  6. 06 hunter > mcp.data.deliver > csv to s3://vzu-data/bayut/yyyy-mm-dd.csv
  7. 07 hunter > mcp.schedule.cron > daily 03:00 utc
  8. 08 hunter > ship. 2 weeks. 50k listings/day. 99.4% success rate.
hunter>

Audit trail · 6 entries

  • T+00:00:00 brief.received
  • T+00:00:30 robots.checked
  • T+00:01:00 scraper.built
  • T+00:08:00 data.delivered
  • T+00:14:00 schedule.setup
  • T+02:00:00 brief.completed

The numbers

HUNTER, by the numbers.

  • 2 weeks

    Median build duration

  • 50,000

    Listings/day

  • 99.4%

    Success rate

  • 5s

    Avg scrape time

Get in touch

Brief HUNTER.

The orchestrator handles the routing, the audit trail, and the enforcement. HUNTER handles the work. The operator owns the goal.