A real browser. Ready for your workflow.
Render dynamic pages, run configured page interactions, and reuse encrypted session profiles in the cloud. Built for repeatable API routes and AI agents.
- Adaptive browser escalationAutomatic or explicit JavaScript rendering.
- Encrypted session profilesReuse an authorized browser profile.
- Scripted route interactionsCapture clean data, screenshots, or PDFs.
Navigate, filter, and capture in one render.
The browser on the left opens a job board and applies its remote filter. The captured result appears on the right, showing how configured actions run in sequence within a single request.
From your input to a useful result.
- Choose a sample input
- Apply the feature’s workflow
- Inspect the result
This example runs entirely in your browser with illustrative data. Use the real feature’s guide and listing to check supported inputs, access rules, and pricing.
Explore the example, then use the setup guide to try the real feature.
Project setup and what to check
Input: A published or draft API route, a buyer API key, and an authorized website workflow. Identify which steps require clicks, text entry, or rendered content.
Workflow: Configure route browser actions to navigate, fill fields, click controls, and wait for the page to settle. Capture Markdown, XHR JSON, a screenshot, or a PDF in the response.
Result: A completed browser render and the extracted data or captured artifact your application needs. Every request runs in an isolated browser context and finishes cleanly.
Confirm your selectors and wait conditions in a test call before publishing. Review whether automatic mode can satisfy static pages without launching a full browser.
Navigate. Interact. Get the result.
Configure browser actions and output formats inside a repeatable API route.
- 1
Choose render mode
Enable JavaScript or automatic escalation on your route.
- 2
Interact with the page
Navigate, fill, click, and wait for the content you need.
- 3
Capture and return
Extract structured data, Markdown, screenshots, or PDFs.
See each step of the workflow.
Configure deterministic browser actions and output formats inside a reusable API route.
- Auto mode avoids the browser fee when a static fetch succeeds.
- Every render runs in an isolated, short-lived browser context.
- Encrypted session profiles stay server-side in Vault blocks.
Action sequence, not an executable configuration. Exact inputs come from your route settings and request headers.
1. open → load permitted target URL
2. fill → enter query in search field
3. click → apply filter or submit form
4. wait_for → confirm result selector rendered
5. extract → capture DOM, XHR, or screenshotRender mode: js or auto
Session: encrypted Vault session_profile, if needed
CAPTCHA: opt-in automated solver when enabled
Output: JSON, Markdown, screenshot, or PDF
Test selectors and wait rules before publishing.Keep an authorized session
Attach encrypted session profiles or bootstrap steps for workflows that need cookies.
Return evidence or structured data
Capture screenshots, PDFs, or intercepted XHR JSON from the rendered page.
Browser execution for web APIs and AI agents
An HTTP fetch cannot complete every web workflow. Some pages need JavaScript execution, a search form submission, a bootstrap cookie, or several clicks before the useful content appears. ApiClay provides stateless per-request cloud browser execution inside published API routes and URL extraction calls.
Configure browser actions once so every caller receives the same documented API contract. Each render runs in an isolated sandbox outside your application process, applies the route's proxy and CAPTCHA settings when enabled, and tears down cleanly as soon as the response is captured.
Automatic browser selection and escalation
ApiClay manages browser rendering automatically behind the auto setting, escalating across standard and hardened browser profiles when a source requires full layout support or returns a blocking challenge.
How it works
Automatic escalation improves compatibility without exposing driver complexity, though it is not a guarantee that every target will permit an automated request.
Reuse authorized session state safely
Encrypted session profiles store approved cookies and origin storage inside Vault blocks for routes that require continuity across stateless calls.
How it works
Session bootstrap can also visit a landing page first to collect fresh cookies and CSRF tokens before the main request runs. Keep session profiles private to trusted operators.
Automate multi-step page workflows
Configured browser actions execute deterministic sequences such as filling a search input, clicking a filter button, scrolling lazy content, and waiting for a target selector before extraction.
How it works
Opt-in automated CAPTCHA solving handles supported challenges on routes that request it without requiring manual intervention.
Capture evidence as well as data
Retrieve full-page screenshots or PDFs when a workflow needs a visual record, or extract structured JSON, clean Markdown, and matching XHR responses for downstream processing.
How it works
Route-level output controls and request headers let callers choose the smallest useful representation for each task.
Where this fits into your work.
Dynamic page extraction
Load a JavaScript application, wait for client-side data to render, and return clean Markdown or intercepted XHR JSON through a documented API route.
Form and filter workflows
Submit a search query, toggle a page filter, and extract the resulting records or screenshot in a single stateless API request.
Authorized portal reads
Attach a restricted Vault session profile or session bootstrap step to read permitted portal pages without distributing cookies to API consumers.
Start with a focused test.
Use these steps to set up Cloud Browser and review the result before making it part of a larger workflow.
Configure a browser route →- 1
Choose a render mode
Enable JavaScript rendering when every call requires a browser, or choose automatic mode so static responses avoid browser overhead and escalate only when needed.
- 2
Configure page actions
Define ordered steps to fill inputs, click controls, scroll, or wait for selectors and network activity. Attach an encrypted session profile or bootstrap URL when authorized.
- 3
Extract and return
Map the rendered DOM or intercepted XHR responses into clean JSON, Markdown, screenshots, or PDFs that callers and MCP agents can consume through one contract.
Understand each workflow’s cost.
Match the feature’s limits and billing model to the work you want to run.
Explore API listings →A browser-rendered call carries the platform browser render fee only when browser execution actually occurs. Proxy bandwidth and verified automated CAPTCHA charges apply separately when a route or caller enables them, and failed calls are refunded automatically.
Static hits in automatic render mode do not incur the browser render charge, and failed CAPTCHA attempts are never billed. Review the listing's Pricing tab and billing response headers to inspect exact per-call usage.
Open an API listing for its Reference, Playground, and Pricing. Check the selected route’s allowances and applicable infrastructure charges before increasing usage.
FAQs
Do I need to run Chromium on my own server?
No. ApiClay runs the isolated browser fleet. Configure render mode and page actions on your route in Publisher Studio or pass supported extraction options at call time.
How do authenticated workflows keep session state?
Store approved cookies in an encrypted Vault session profile block or configure session bootstrap to visit a login or landing URL before the main request executes.
Does auto mode always launch a browser?
No. Auto rendering starts with a static fetch where possible and promotes to browser execution when the response requires it. A successful static result avoids the browser-render fee.
Are browser contexts shared across requests?
No. Each render executes in an isolated, sandboxed browser context that is destroyed when the request finishes. Stored session profiles are encrypted and tenant-bound.
Bring the browser into your workflow.
Test a dynamic source and build a repeatable browser-backed API.