Integrations

Massive (web rendering)

Connect Massive to fetch hard-to-retrieve web pages. Massive is available both as a built-in Agent tool and as a fetch method on the Fetch URL Flow step, alongside Firecrawl.

What is Massive?

Massive’s Web Render API turns hard-to-reach web content into clean data. It renders JavaScript, solves captchas, and retries requests through a residential network, which makes it a good fit for pages that block or challenge datacenter traffic. Pages can be returned as LLM-optimized markdown, rendered HTML, or raw HTML, and requests can be geotargeted by country.

Setting up Massive

Massive is available through platform keys, so you can use it without providing your own API key. If you want to use your own Massive account:

  1. Sign up at joinmassive.com
  2. Get your API token from the dashboard
  3. In Runtype, go to Settings → Integrations
  4. Find Massive
  5. Enter your API token
  6. Click Save Key

Using Massive as a tool

Enable the Massive Web Render built-in tool when configuring an Agent. The Agent can then autonomously fetch pages that resist ordinary HTTP requests.

The tool accepts:

  • url (required) — The page to fetch
  • format — Output format: markdown (default), rendered (post-JavaScript HTML), or raw (unrendered HTML)
  • country — Two-letter ISO country code to fetch from (for example us)
  • delay — Supplemental seconds (0.1 to 10) to wait before capturing content on slow-loading pages

Using Massive in a Flow

On the Fetch URL step, set the fetch method to Massive (Web Render). The step then routes the request through Massive instead of a raw HTTP fetch, with options for output format, geotargeting, snapshot delay, and cache expiration.

When to choose Massive vs Firecrawl

Both services fetch pages that block ordinary requests. Firecrawl adds structured extraction options (JSON extraction, page actions, main-content stripping). Massive focuses on unblocking difficult sites, with residential geotargeting and captcha solving. If one service cannot retrieve a page, try the other.

Use cases

  • Hard-to-reach pages: Fetch sites that block, rate-limit, or challenge datacenter traffic
  • Localized content: Fetch pages as seen from a specific country
  • Dynamic pages: Capture content that only appears after JavaScript runs
  • Research: Gather data from sources that resist ordinary scraping

Next steps