API docs first
See auth headers, endpoint bodies, browser settings, and response structures before switching into the dashboard.
Support
Use docs, playground, and dashboard together
The support experience stays close to implementation: inspect request shapes, test browser settings, and move into the console when you are ready.
Code-shaped guidance
Use cURL, Node.js, and Python examples that mirror the same request language used by the product UI.
Key-aware troubleshooting
Validate API key usage, session ownership, and request parameters from one predictable workflow.
Focused onboarding
Clarify which endpoint, output format, and browser settings fit your real automation or extraction task.
Why this layout works
Designed for technical evaluation, not marketing noise
The homepage now mirrors the strengths of good API-product sites: strong hierarchy, direct value communication, and short paths to code and docs.
API-first storytelling
The homepage explains outputs, auth, and browser control using the same structure users see later in docs and dashboard pages.
Operational clarity
Screenshots, extraction, and remote sessions live in one narrative so the product feels coherent rather than scattered.
SEO-aware content structure
A clear H1-to-H3 hierarchy, internal links, use-case copy, and FAQ content make the page easier for both users and crawlers.
FAQ
Questions teams ask before integrating
The FAQ is part of the page architecture, not an afterthought. It clarifies product scope while supporting search visibility.
What can I do with this platform on day one?
You can start with HTTP endpoints for screenshots and content extraction, then move to remote CDP sessions when you need full browser automation.
Is this only for scraping?
No. It also works for page QA, rendering verification, SEO review, content ingestion, and browser-based automation backends.
How does authentication work?
The product uses x-api-key authentication across the docs, dashboard proxy routes, and production-facing browser endpoints.
When should I use remote CDP instead of HTTP capture?
Use HTTP capture when you need fast screenshots or extracted content. Use remote CDP when you need a live session for step-by-step automation.
Ready to start
Try it once, then decide how it should fit your stack
The homepage ends with one clear action so attention comes back to sign-up and evaluation.