Browserless: 5 writes, one client

Hosted Chrome as an HTTP API — screenshot, PDF, scrape and run arbitrary page functions. Free plan: 1,000 units a month. Every call below is available over HTTP, through the SDK and as a tool for a coding agent, with the same arguments and the same meter.

What Browserless can do here

The integration exposes 5 writes, each with a declared input and output schema rather than a page of documentation you would have to translate. Hosted Chrome as an HTTP API — screenshot, PDF, scrape and run arbitrary page functions. Free plan: 1,000 units a month.

How it authenticates

Browserless authenticates with a token, supplied per request or stored once against your account and sealed at rest. On our side the same value is read from token when we broker the call for you.

Called by name, not by capability

Browserless does not currently map onto a vendor-neutral capability, so you call its operations by name. That is the right shape when you genuinely mean this provider — which, for a service with its own model of the world, is most of the time.

• content — write: Fully rendered HTML of a page, after JavaScript has run.
• screenshot — write: Screenshot a page. Returns IMAGE BYTES.
• pdf — write: Render a page as a PDF. Returns PDF BYTES.
• scrape — write: Extract structured data from a page using CSS selectors.
• function — write: Run arbitrary JavaScript in a real browser and return what it produces — the escape hatch when the fixed endpoints will not do.

Questions

Do I have to bring my own API keys?

You can, and that lane is free for ever — pass your key on the request or store it against your account, and we are one proxy hop. The paid lane is the other direction: we call 226 providers with our credentials so you never register anywhere. Both go through the same client and the same operation names.

What happens to a key I store here?

It is sealed with AES-256-GCM before it reaches the database and is only ever opened to make the call you asked for. It is scoped to your account, it is never logged, and deleting the connection deletes it. For an OAuth provider we hold a refresh token instead, and revoking the link at the provider stops the calls here immediately.

What happens when a provider changes its API?

The operation contract is declared, so a response that no longer matches is a refusal rather than a silently wrong answer. The contract does not coerce types — a field declared a number that arrives as a string is rejected at the edge, on the way in and on the way out.