Browserless
One call in, a rendered result out: screenshot, PDF, HTML, or a CSS-selector scrape from a single page load.
Use Browserless here without a subscription. Browserless sells its API only in monthly plans, per its pricing page; through NativePort you pay per call from one balance.
Where Browserless lands
No score or rank is published until the shared benchmark corpus covers Browserless — the note below carries the reason. Full method: how we measure.
The honest pitch
Reach for it when the job is a single page — grab a screenshot, PDF, rendered HTML, or a structured CSS-selector scrape — and there's no session to keep alive.
Not the pick for a multi-step, stateful flow: driving a Playwright/Puppeteer session yourself, logins, or anything spanning more than one page load sits outside this route.
About Browserless
Browserless answers four fixed actions — screenshot, PDF, rendered HTML, and a structured CSS-selector scrape — each one page load, one response, capped at a 30-second bound per call. The credential that talks to Browserless never leaves the gateway; every call runs on the same NativePort key and balance as the rest of the catalog, billed a flat rate per accepted attempt. It’s the fast, single-call complement to a stateful browser session rather than a substitute for one: reach for Browserless when the ask is ‘render this page and hand back the result,’ and reach for a session-oriented browser product when the job needs multiple steps or ongoing state.
Reaching it through NativePort
Identical paths, parameters and responses to Browserless's own documentation — the gateway holds the upstream credential and meters your balance at Browserless's real published usage price.
curl https://api.nativeport.ai/browserless/<native-path> \ -H "Authorization: Bearer $NATIVEPORT_API_KEY"