← All speakers

Bio, Work & Ideas

Rafael Levi

Conference affiliation: Bright Data · 2026

Rafael Levi is a developer-relations professional and web-data specialist at Bright Data who helps AI agents retrieve reliable, current public information. He focuses on a foundational weakness of automated research: agents can produce convincing answers even when blocked requests, CAPTCHAs, empty responses, or outdated data prevent them from accessing the web.

In early 2024, Levi was a senior solutions consultant at Bright Data, advising developers on proxy selection, browser automation, infrastructure, and scraping reliability. Later that year, as a senior solution architect, he tackled large-scale travel-data collection, including rapidly changing fares, anti-bot defenses, cloud-hosted browsers, and parallel browsing sessions. He subsequently brought that infrastructure experience into developer relations and AI-agent workflows.

  • Silent web-access failures: Agents may substitute stale training data or fabricate plausible answers when a public page is blocked or unavailable. Levi demonstrates these failure modes across property, professional-networking, social-media, and shopping websites, arguing that trustworthy agents must distinguish successful retrieval from apparent access.
  • Reusable agent-generated scrapers: Levi uses Claude Code, Bright Data's public-web MCP server, and its agent skills repository to inspect websites, identify selectors, and generate conventional extraction scripts. Running those scripts directly avoids repeatedly processing entire pages through a language model and produces structured data that can be scheduled and validated. These repositories belong to Bright Data; Levi demonstrates their application without claiming personal authorship.
  • Self-healing data pipelines: His production-oriented extraction workflows monitor recurring collection jobs, flag missing fields or changed website structures, and use agents to repair broken scrapers. Applications range from commercial research to alerts for public housing listings.
  • Public-data boundaries and focused tools: Levi limits these workflows to publicly accessible information, distinguishes it from material behind authenticated accounts, and advises checking website terms. He also favors selectively enabling relevant MCP tools, preventing unnecessary capabilities from consuming an agent's context.

More recently, Levi has applied the same retrieval concerns to video discovery for agentic world models, identifying useful scenes, actions, objects, and environments in public video for training-oriented workflows.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

A live headphones search shows how an agent can inspect a protected website, generate a reusable scraper, and reserve model work for building, checking, and repairing the pipeline.

  • Ten thousand products should not mean ten thousand LLM extractions
    0:17 ↗
  • The scraper tax continues after the first successful run
    1:16 ↗
  • Give the agent a reusable interface
    2:27 ↗
  • The same pattern works for a shopping question
    4:58 ↗
  • An old scraper forces a fresh test
    6:00 ↗
  • From a search to a scheduled listener
    8:01 ↗
  • Choose the right web-access interface
    10:08 ↗
  • Walmart returns a verification screen, then product data
    11:38 ↗
  • Measure the extraction, then keep checking it
    13:36 ↗
  • Inspect the Python scraper, then change its inputs
    15:33 ↗
  • Public access does not remove terms and legal constraints
    17:44 ↗
  • Retrieving results and reading them are different costs
    19:24 ↗
  • Protected sites and listeners that wait
    21:45 ↗
  • When the pipeline needs to click
    23:01 ↗

Key ideas

Scroll to read ↓

Reliable web agents need more than plausible answers: they need usable retrieval tools, explicit failure reporting, and a clear distinction between accessing a page and verifying its contents.

  • What evidence is behind the answer?
    0:19 ↗
  • Five URLs, with no browsing tools
    3:01 ↗
  • What the MCP connection adds
    4:52 ↗
  • Public visibility is an access boundary
    6:52 ↗
  • Choose freshness, then inspect the result
    8:43 ↗
  • Avoiding a block does not verify the content
    9:51 ↗
  • Have the model build the parser
    12:26 ↗
  • Expose only the tools the task needs
    13:41 ↗
  • The experiment tested URL access, not web search
    14:07 ↗
  • A monthly allowance for experiments
    15:07 ↗

References