zyte-fetch

name: zyte-fetch description: Fetch web pages via Zyte API with browser rendering (client-side JavaScript execution). Use when you need to retrieve content from websites that require JavaScript rendering, or when standard web_fetch returns incomplete/empty content due to client-side rendering. Also useful for anti-bot bypass, screenshots, and structured data extraction (article, product, job posting, SERP, page content).

Zyte Fetch

Fetch web pages through Zyte API. Supports browser-rendered HTML (JavaScript executed), plain HTTP, screenshots, and structured data extraction.

API Key

Resolved in order: ZYTE_API_KEY env var → file at ZYTE_API_KEY_FILE → ~/.config/zyte/api_key.

Quick Start

Browser-rendered HTML (default — handles JS-heavy sites)

scripts/zyte_fetch.sh "https://example.com"

Plain HTTP (faster, no JS)

scripts/zyte_fetch.sh "https://example.com" --http

Screenshot

scripts/zyte_fetch.sh "https://example.com" --screenshot --output page.html
# Saves page.html + page.png

Raw JSON response

scripts/zyte_fetch.sh "https://example.com" --raw-json

Structured extraction

Extract structured data from the page. Only one type can be used per request.

# Article (e.g. news, Wikipedia)
scripts/zyte_fetch.sh "https://en.wikipedia.org/wiki/Lobster" --article

# Product (e-commerce pages)
scripts/zyte_fetch.sh "https://example.com/product/123" --product

# Job posting
scripts/zyte_fetch.sh "https://example.com/jobs/456" --job-posting

# Search engine results page
scripts/zyte_fetch.sh "https://www.google.com/search?q=example" --serp

# Cleaned page content (noise-free body text)
scripts/zyte_fetch.sh "https://example.com" --page-content

When to Use

• web_fetch returns empty/broken content → use zyte_fetch.sh (browser mode)
• Site has anti-bot protection → Zyte handles proxy rotation and fingerprinting
• Need a screenshot of a rendered page → use --screenshot
• Need structured article/product/job data → use --article / --product / --job-posting
• Need clean body text → use --page-content
• Simple static page → prefer web_fetch (free, faster)

Direct curl (advanced)

API_KEY="${ZYTE_API_KEY:-$(cat ~/.config/zyte/api_key)}"
curl -s --compressed --user "${API_KEY}:" \
  -H 'Content-Type: application/json' \
  -d '{"url":"https://example.com","browserHtml":true}' \
  https://api.zyte.com/v1/extract | jq -r .browserHtml

Structured extraction example:

API_KEY="${ZYTE_API_KEY:-$(cat ~/.config/zyte/api_key)}"
curl -s --compressed --user "${API_KEY}:" \
  -H 'Content-Type: application/json' \
  -d '{"url":"https://en.wikipedia.org/wiki/Lobster","article":true}' \
  https://api.zyte.com/v1/extract | jq '.article'

API Reference

• Endpoint: POST https://api.zyte.com/v1/extract
• Auth: Basic auth with API key as username, empty password
• Key request fields:
  • url (required): Target URL
  • browserHtml: true: Get JS-rendered HTML
  • httpResponseBody: true: Get raw HTTP response (base64)
  • screenshot: true: Get screenshot (base64 PNG)
  • article: true: Extract structured article data
  • product: true: Extract structured product data
  • jobPosting: true: Extract structured job posting data
  • serp: true: Extract structured search engine results page data
  • pageContent: true: Extract cleaned page content
• See full docs for geolocation, actions, cookies, sessions, etc.