Browsers

An index and topic collection covering programmable browsers, headless browser engines, and browser-automation APIs. The Browsers topic focuses on the browser execution surface — the runtime where pages are loaded, JavaScript is evaluated, and interactions are scripted — including local libraries like Puppeteer, Playwright, and Selenium, as well as managed browser-as-a-service platforms used for automation, data extraction, agentic web tasks, and cross-browser testing. This collection is distinct from web scraping and pure test-runner topics; it emphasizes the browser instance, session, and navigation surface that other automation, scraping, and AI-agent capabilities build on top of.

Browsers is profiled on the APIs.io network. Tagged areas include Headless Browser, Browser Automation, Web Automation, Browser-as-a-Service, and WebDriver.

The Browsers catalog on APIs.io includes 1 JSON-LD context.

Browsers’ developer surface includes developer portal and 1 more developer resources.

9.6/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0
0 APIs 8 Features 8 Use Cases
Headless BrowserBrowser AutomationWeb AutomationBrowser-as-a-ServiceWebDriverBrowser Testing

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/browsers: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Features 8

Notable capabilities this provider offers.

Headless Browser Execution

Programmable browser runtimes like Chromium, WebKit, and Gecko driven without a visible UI for automated navigation, rendering, and DOM interaction.

Browser Automation Libraries

Client libraries like Puppeteer, Playwright, and Selenium that expose a high-level API for controlling browser sessions, pages, frames, and inputs.

Browser-as-a-Service

Managed cloud platforms that provision pre-warmed browser instances over WebSocket, CDP, or HTTP so consumers do not have to host their own browser fleet.

Session and Profile Management

APIs for creating, persisting, and reusing browser sessions, cookies, localStorage, fingerprints, and authenticated profiles across runs.

Navigation and DOM Interaction

A consistent surface for navigating to URLs, waiting for selectors, clicking, typing, scrolling, evaluating JavaScript, and capturing rendered DOM state.

Network and Stealth Controls

Proxy routing, header and user-agent customization, request interception, and anti-bot evasion controls layered on top of the browser instance.

Capture and Artifact APIs

Endpoints for screenshots, full-page PDFs, HAR network logs, video recordings, and trace files generated from automated browser sessions.

Agent-Ready Browser Surfaces

AI-agent oriented interfaces, including Model Context Protocol servers and natural-language navigation, that expose a browser as a tool for LLMs.

Scroll for all 8

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Browsers Context

8 classes · 20 properties

JSON-LD

JSON Schema 2

Standalone JSON Schema definitions for this provider's data models.

BrowserSession

12 properties

JSON SCHEMA

NavigationAction

10 properties

JSON SCHEMA

JSON Structure 2

JSON Structure definitions describing this provider's data shapes.

Browsers Browser Session Structure

12 properties

JSON STRUCTURE

Browsers Navigation Action Structure

10 properties

JSON STRUCTURE

Examples 2

Example request and response payloads for these APIs.

Use Cases 8

What developers build with this provider.

Automated Web Data Extraction

Drive a real browser to render JavaScript-heavy pages and extract structured data that static HTTP scraping cannot reach.

Cross-Browser End-to-End Testing

Run application tests against Chromium, Firefox, and WebKit on real or virtualized devices to validate behavior before release.

Synthetic Monitoring and Uptime Checks

Schedule scripted browser flows to continuously verify that critical user journeys remain functional in production.

Agentic Web Task Execution

Provide AI agents with a controlled browser session so they can complete multi-step tasks like form filling, booking, and research.

Visual and PDF Generation

Render web content to high-fidelity screenshots, social-share images, or PDF reports on demand via a managed browser API.

Authenticated Session Automation

Maintain logged-in browser profiles so automation can perform actions inside customer-account areas across runs.

Accessibility and Performance Audits

Execute Lighthouse, axe, and similar audits inside a real browser to track accessibility and performance regressions over time.

Legacy Application Robotics

Use browser automation as a UI-layer integration mechanism for systems that lack a usable API.

Scroll for all 8

Integrations 8

Pre-built integrations with other platforms and tools.

Playwright

Open-source browser automation library from Microsoft that drives Chromium, Firefox, and WebKit through a unified API.

Puppeteer

Node.js library from the Chrome team that controls headless Chromium via the Chrome DevTools Protocol.

Selenium

Long-standing browser automation suite built around WebDriver, used heavily for cross-browser end-to-end testing.

BrowserStack

Cloud browser and device platform providing real browsers and devices for automated and live cross-browser testing.

Bright Data Scraping Browser

Managed remote browser endpoint with built-in proxies and anti-bot infrastructure for large-scale automation.

Apify

Web automation platform whose Actors run Puppeteer and Playwright workloads at scale on managed infrastructure.

Browser Use

AI-agent oriented library that gives LLMs a controllable browser as a tool surface for autonomous web tasks.

Checkly

Synthetic monitoring platform that runs Playwright scripts on a schedule to validate production user journeys.

Scroll for all 8

Resources

Get Started 1

Portal, sign-up, and the first successful call

Build 1

SDKs, sample code, and the tooling you integrate with

Source (apis.yml)

apis.yml Raw ↑
aid: browsers
name: Browsers
description: An index and topic collection covering programmable browsers, headless browser engines, and browser-automation
  APIs. The Browsers topic focuses on the browser execution surface — the runtime where pages are loaded, JavaScript is evaluated,
  and interactions are scripted — including local libraries like Puppeteer, Playwright, and Selenium, as well as managed browser-as-a-service
  platforms used for automation, data extraction, agentic web tasks, and cross-browser testing. This collection is distinct
  from web scraping and pure test-runner topics; it emphasizes the browser instance, session, and navigation surface that
  other automation, scraping, and AI-agent capabilities build on top of.
type: Index
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Headless Browser
- Browser Automation
- Web Automation
- Browser-as-a-Service
- WebDriver
- Browser Testing
url: https://raw.githubusercontent.com/api-evangelist/browsers/refs/heads/main/apis.yml
created: '2026-05-19'
modified: '2026-05-19'
specificationVersion: '0.19'
apis: []
network:
- name: AgentQL
  url: https://raw.githubusercontent.com/api-evangelist/agentql/refs/heads/main/apis.yml
- name: Apify
  url: https://raw.githubusercontent.com/api-evangelist/apify/refs/heads/main/apis.yml
- name: API Snap
  url: https://raw.githubusercontent.com/api-evangelist/api-snap/refs/heads/main/apis.yml
- name: Appium
  url: https://raw.githubusercontent.com/api-evangelist/appium/refs/heads/main/apis.yml
- name: Apple Safari
  url: https://raw.githubusercontent.com/api-evangelist/apple-safari/refs/heads/main/apis.yml
- name: Bright Data
  url: https://raw.githubusercontent.com/api-evangelist/bright-data/refs/heads/main/apis.yml
- name: Browser Use
  url: https://raw.githubusercontent.com/api-evangelist/browser-use/refs/heads/main/apis.yml
- name: BrowserStack
  url: https://raw.githubusercontent.com/api-evangelist/browserstack/refs/heads/main/apis.yml
- name: Checkly
  url: https://raw.githubusercontent.com/api-evangelist/checkly/refs/heads/main/apis.yml
- name: Crawlee
  url: https://raw.githubusercontent.com/api-evangelist/crawlee/refs/heads/main/apis.yml
- name: Cucumber
  url: https://raw.githubusercontent.com/api-evangelist/cucumber/refs/heads/main/apis.yml
- name: Google Chrome
  url: https://raw.githubusercontent.com/api-evangelist/google-chrome/refs/heads/main/apis.yml
- name: Microsoft Edge
  url: https://raw.githubusercontent.com/api-evangelist/microsoft-edge/refs/heads/main/apis.yml
- name: Microsoft Playwright
  url: https://raw.githubusercontent.com/api-evangelist/microsoft-playwright/refs/heads/main/apis.yml
- name: Playwright
  url: https://raw.githubusercontent.com/api-evangelist/playwright/refs/heads/main/apis.yml
- name: Puppeteer
  url: https://raw.githubusercontent.com/api-evangelist/puppeteer/refs/heads/main/apis.yml
- name: Scrapfly
  url: https://raw.githubusercontent.com/api-evangelist/scrapfly/refs/heads/main/apis.yml
- name: ScrapingAnt
  url: https://raw.githubusercontent.com/api-evangelist/scrapingant/refs/heads/main/apis.yml
- name: ScrapingBee
  url: https://raw.githubusercontent.com/api-evangelist/scrapingbee/refs/heads/main/apis.yml
- name: Selenium
  url: https://raw.githubusercontent.com/api-evangelist/selenium/refs/heads/main/apis.yml
- name: Servo
  url: https://raw.githubusercontent.com/api-evangelist/servo/refs/heads/main/apis.yml
common:
- type: Portal
  url: https://apievangelist.com
- type: GitHubOrganization
  url: https://github.com/api-evangelist
- type: Features
  data:
  - name: Headless Browser Execution
    description: Programmable browser runtimes like Chromium, WebKit, and Gecko driven without a visible UI for automated
      navigation, rendering, and DOM interaction.
  - name: Browser Automation Libraries
    description: Client libraries like Puppeteer, Playwright, and Selenium that expose a high-level API for controlling browser
      sessions, pages, frames, and inputs.
  - name: Browser-as-a-Service
    description: Managed cloud platforms that provision pre-warmed browser instances over WebSocket, CDP, or HTTP so consumers
      do not have to host their own browser fleet.
  - name: Session and Profile Management
    description: APIs for creating, persisting, and reusing browser sessions, cookies, localStorage, fingerprints, and authenticated
      profiles across runs.
  - name: Navigation and DOM Interaction
    description: A consistent surface for navigating to URLs, waiting for selectors, clicking, typing, scrolling, evaluating
      JavaScript, and capturing rendered DOM state.
  - name: Network and Stealth Controls
    description: Proxy routing, header and user-agent customization, request interception, and anti-bot evasion controls layered
      on top of the browser instance.
  - name: Capture and Artifact APIs
    description: Endpoints for screenshots, full-page PDFs, HAR network logs, video recordings, and trace files generated
      from automated browser sessions.
  - name: Agent-Ready Browser Surfaces
    description: AI-agent oriented interfaces, including Model Context Protocol servers and natural-language navigation, that
      expose a browser as a tool for LLMs.
- type: UseCases
  data:
  - name: Automated Web Data Extraction
    description: Drive a real browser to render JavaScript-heavy pages and extract structured data that static HTTP scraping
      cannot reach.
  - name: Cross-Browser End-to-End Testing
    description: Run application tests against Chromium, Firefox, and WebKit on real or virtualized devices to validate behavior
      before release.
  - name: Synthetic Monitoring and Uptime Checks
    description: Schedule scripted browser flows to continuously verify that critical user journeys remain functional in production.
  - name: Agentic Web Task Execution
    description: Provide AI agents with a controlled browser session so they can complete multi-step tasks like form filling,
      booking, and research.
  - name: Visual and PDF Generation
    description: Render web content to high-fidelity screenshots, social-share images, or PDF reports on demand via a managed
      browser API.
  - name: Authenticated Session Automation
    description: Maintain logged-in browser profiles so automation can perform actions inside customer-account areas across
      runs.
  - name: Accessibility and Performance Audits
    description: Execute Lighthouse, axe, and similar audits inside a real browser to track accessibility and performance
      regressions over time.
  - name: Legacy Application Robotics
    description: Use browser automation as a UI-layer integration mechanism for systems that lack a usable API.
- type: Integrations
  data:
  - name: Playwright
    description: Open-source browser automation library from Microsoft that drives Chromium, Firefox, and WebKit through a
      unified API.
  - name: Puppeteer
    description: Node.js library from the Chrome team that controls headless Chromium via the Chrome DevTools Protocol.
  - name: Selenium
    description: Long-standing browser automation suite built around WebDriver, used heavily for cross-browser end-to-end
      testing.
  - name: BrowserStack
    description: Cloud browser and device platform providing real browsers and devices for automated and live cross-browser
      testing.
  - name: Bright Data Scraping Browser
    description: Managed remote browser endpoint with built-in proxies and anti-bot infrastructure for large-scale automation.
  - name: Apify
    description: Web automation platform whose Actors run Puppeteer and Playwright workloads at scale on managed infrastructure.
  - name: Browser Use
    description: AI-agent oriented library that gives LLMs a controllable browser as a tool surface for autonomous web tasks.
  - name: Checkly
    description: Synthetic monitoring platform that runs Playwright scripts on a schedule to validate production user journeys.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
humanURL: https://apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/browsers"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/browsers/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/browsers/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.