Credential boundaries
API keys, cookies, proxy credentials, provider tokens, and browser connection details stay outside public result payloads.
Security
Security built into the data path
Public-safe controls, explicit runtime ownership, and audit evidence are part of the collection path, not an afterthought.
Request policy
Public targets and redirects pass server-owned URL and egress validation before acquisition.
Scoped authorization
Product, Admin, Ops, and public API surfaces keep explicit route and role boundaries.
Managed browser lifecycle
Profile leases, capacity admission, health, release, cooldown, and cleanup remain behind the browser gateway.
Audit evidence
Request IDs, engine attempts, fallback reasons, quality decisions, and cost units support investigation without exposing raw secrets.
Bounded execution
Timeouts, response limits, retry budgets, crawl scope, and queue ownership reduce uncontrolled work.
Public responseUseful evidence
Normalized output, status, diagnostics, and request IDs.
Private runtimeProtected internals
Credentials, profiles, proxies, CDP details, and raw provider state.
Start building
Build on an explicit security boundary.
Review the public API contract, then validate your intended workflow against the available controls and result fields.