NewIntroducing semantic snapshotsPair every capture with structured DOM data →
domscout

Progress

Explore the platform

Browser captures, structured extraction and durable workflows, with the controls and billing information you need to use them.

Get your free API key Read the longer write-ups
  1. 01FoundationShipped

    One endpoint that renders a page properly

    Send a URL and receive an image of the page rendered in Chromium. Choose the viewport, output format and page region your workflow needs.

    • Captures run in headless Chromium. Use selector waits or lazy scrolling when content needs an additional readiness step.
    • PNG, JPEG and WebP from one endpoint, with device presets, custom viewports, and locale and timezone emulation.
    • Element and full-page capture, so the result can be the part of the page that matters rather than a default viewport.
  2. 02ExtractionShipped

    Page content as Markdown and structured data

    Read a page as Markdown, inspect its interactive structure, or extract fields with CSS selectors. Combine outputs when you need both content and a visual record.

    • extractMarkdown returns the rendered page as tidy Markdown: headings, tables, lists, links and alt text survive; script soup, inline styles and hydration artefacts do not.
    • Every extraction reports its own markdownMeta.estimatedTokens and a content-quality assessment, so the reduction is measurable per page instead of asserted.
    • Semantic snapshots walk the accessibility tree and return scored selectors for each node - structure a model or a test can address, not a screenshot it has to guess at.
    • Selector-based field extraction for the cases where you know exactly what you want off the page.
  3. 03DurabilityShipped

    Durable jobs for larger runs

    Submit a batch or crawl as a durable job, poll its progress, and read each child's result independently. A long run can resume work after an interruption.

    • Crawl and batch workflows provide per-child results and optional webhook callbacks when a run finishes.
    • Retries preserve completed child work so a resumed run can continue from its recorded progress.
    • Idempotency keys mean a resubmitted run is the same run, so a client retry cannot silently start a second crawl.
    • Quota is charged when a child actually starts, never when a parent is created - a job that never ran costs nothing.
  4. 04PricingShipped

    Credit pricing visible before a run

    Requests use credits according to the outputs and options selected. The pricing page lists plan allowances and retention periods, and GET /credits returns your balance and the current price list.

    • Every plan states its included quota, rate limit and capture retention period.
    • Paid plans meter overage up to twice the included quota, then refuse further usage beyond the ceiling.
    • The free Hobby plan stops at its allowance and cannot accrue metered overage.
    • The playground shows an estimated request cost as you choose capture options.
  5. 05Request limitsShipped

    Public targets and bounded workflows

    Capture public HTTP and HTTPS pages within the limits of your plan. Request refusals carry codes and guidance so your application can decide whether to correct the input or retry later.

    • Private-address targets and URLs containing credentials are refused.
    • Crawl page counts, browser options and scheduled monitor capacity have explicit plan limits.
    • Use durable job identifiers to poll progress or request cancellation.
  6. 06SurfaceShipped

    Explore the API before connecting your application

    Use the product pages and API documentation to choose a workflow, then try a basic capture in the public playground before creating an API key.

    • Every capability has its own page, and the docs remain the single guide to the API.
    • Light and dark themes across the marketing site and the dashboard alike.
    • The playground runs a real capture without an account, so the product can be evaluated before it is signed up for.
    • Request examples show the method, fields and API-key header needed to connect your application.
  7. 07AutomationShipped

    Connect an application or an MCP client

    Call the REST API from your application or connect the MCP server to an assistant. Both interfaces use your API key and the same account allowance.

    • MCP tools cover Markdown, screenshots, structured extraction, automation and job polling.
    • Recurring monitors compare the page checks you enable and can notify a webhook when a change is detected.
    • The API reference describes plan gates, credit costs and error codes for each workflow.

Want to change what comes next?

Send a question, feature request or reproducible issue through POST /feedback on any plan. Include the request identifier and the result you expected to help us understand it.

How to send feedback we can act on