Skip to content
VZU
VZU OS Agent running 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.

  • Capability

    VZU Scrape

  • Category

    automation

  • Runtime

    NetWit OS

  • Tools

    5

AGENT · 12
automation

Powers

VZU Scrape

scrape

Portrait

HUNTER, in three dimensions.

Each VZU agent gets a unique geometry. The wireframe is the contract. The fill is the implementation. The particles are the MCP servers the agent can call. Touch the portrait to make it respond.

  • · Geometry: Custom
  • · Color: mist
  • · Wireframe: layer 2
  • · Particles: 80 (MCP servers)

HUNTER · automation

Agent · 00

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.

Live execution trace from a recent HUNTER run. The agent was briefed: Scrape the Bayut property listings daily. 50,000+ listings. Photos, prices, locations. CSV output to S3.. Each line is a step. Particles flow on the rail. The audit trail streams at the bottom.

hunter@vzu-os — trace.log live
  1. 01
    hunter read brief

    read brief

  2. 02
    hunter thinking: bayut scraper. 50k+ listings. daily. 2 weeks.

    thinking: bayut scraper. 50k+ listings. daily. 2 weeks. : bayut scraper. 50k+ listings. daily. 2 weeks.

  3. 03
    hunter mcp.robots.check

    allowed paths: /properties/*, /agents/* : /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. done

    ship. 2 weeks. 50k listings/day. 99.4% success rate.

hunter@vzu-os $

Audit trail · 6 entries

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

The numbers

HUNTER, by the numbers.

Four KPIs. Animated count-up on scroll. Sparkline shows the recent trend. Delta indicator shows the trajectory.

  • KPI · 01 now

    2 weeks

    Median build duration

    47%
  • KPI · 02 now

    50,000

    Listings/day

    3%
  • KPI · 03 now

    99.4%

    Success rate

    33%
  • KPI · 04 now

    5s

    Avg scrape time

    52%

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.