Web Scraping {API}

No. You are not billed for failed requests or requests where we are blocked (rarely happens). Credits are only consumed on successful responses.

Send a GET request to /v1/web/scrape/html?url=<target>. The API fetches the page, transparently rotates proxies if the direct request is blocked, and returns the raw HTML plus the final resolved URL. One call, no setup.

When the direct fetch is blocked or rate-limited, the API automatically escalates through a rotating proxy pool with realistic browser fingerprints. You don't configure anything — the same endpoint works whether the target is open or hard-protected. Pay-as-you-go: simple URLs bill cheap, hard ones bill the fair cost of the bypass.

Yes. JavaScript rendering is available so single-page apps and dynamically populated pages return the post-render HTML, not the empty shell. The API picks the right rendering strategy automatically based on the target.

Same single-call ergonomics — pass URL, get HTML — but bundled with the rest of the Context.dev brand-data stack. One API key gets you scraping plus logos, colors, fonts, NAICS, SIC, transaction enrichment. Pricing is per-call, not per-tier, and the free tier is real (not a 3-day trial).

The HTML endpoint returns the raw source, exactly as served by the target. The Markdown endpoint converts it to clean GitHub Flavored Markdown — better for feeding into LLMs and RAG pipelines because it strips ads, nav chrome, and HTML noise. Use HTML when you need exact DOM, Markdown when you need readable text.

Scraping public web data is generally legal in the U.S. (per hiQ Labs v. LinkedIn). You're responsible for respecting target sites' Terms of Service, robots.txt, and rate limits, and for handling personal data per GDPR/CCPA. The API is a tool — how you use it is your responsibility.

Yes — the free tier covers thousands of monthly scrapes, more than enough for prototyping. Bulk and production pricing scales linearly without forced annual commitments.