Use cases

Make better use
of what’s on the web.

Research competitors, build content briefs and give your AI useful source material.

01 / Page capture

Bring public pages into your application.

Queue single-page or batch scrapes, keep the job reference, and retrieve capture content and metadata when the run completes.

Public URL → Queued scrape
Job state + capture result
Workflow details
Input
Public HTTP or HTTPS pages.
Output
Job status, page content, capture metadata and available artifacts.
Who it serves
Developers building AI applications, research tools and data workflows.
Example
Capture a public product page and let your application process the returned content.

02 / Bounded site collection

Discover and collect a defined part of a site.

Use URL maps to discover same-origin pages, then submit a crawl with explicit depth and page limits. Partial outcomes remain visible.

Same-origin links → URL map
Up to 500 pages · depth up to 3
Workflow details
Input
A public starting URL and crawl bounds.
Output
Discovered URLs, per-page outcomes and captures for successfully crawled pages.
Who it serves
Teams collecting documentation, catalogs or other bounded public content.
Example
Map a documentation site, review discovered pages, then crawl a selected bounded scope.

03 / Dynamic pages

Capture content rendered by JavaScript.

Request browser rendering with capped waits and a small set of bounded click or scroll actions. The API applies network controls to browser subrequests.

Page load → Rendered capture
Bounded actions + optional screenshot
Workflow details
Input
A public page and supported render options.
Output
Rendered page content, job status and available capture artifacts.
Who it serves
Applications that need content added after an initial HTML response.
Example
Render a public page after load and use a bounded action to reveal a content panel.

Marketing research

Build your next brief on real sources.

Collect competitor landing pages, extract messaging and product details, and keep the original sources alongside your analysis.

Explore Marketing and SEO →
Workflow details
Input
Selected public competitor pages.
Output
Saved content and structured fields for your research.
Next step
Use your AI to synthesize a brief, checking its claims against the sources.

Content monitoring

Notice the changes that matter.

Monitor a page, compare saved versions and review audit transitions. Use supported webhooks to bring events into your workflow.

Workflow details
Input
A page, schedule and explicit baseline.
Output
Content differences, comparable findings and delivery history.
Coverage
Failed collection does not mean content was removed. Queued notifications are not confirmed deliveries.

Search evidence and availability

Saved CSS extraction, PDF text with supported OCR languages, monitoring and bounded audits are implemented. Imported SERP comparisons retain unverified provenance. Native Search is experimental; verified live rankings require separate acceptance; Search Console supports authorized properties. Subscription controls are implemented; paid checkout is not yet available. See the product overview ↗.