Kernel
Kernel is browser infrastructure for AI agents and automations. It runs sandboxed cloud Chromium browsers that spin up in under 30ms, with Playwright execution, computer-use controls, managed authentication into third-party sites, reusable browser profiles, proxies, pre-warmed browser pools, session replays, live telemetry, and a serverless App platform for deploying and invoking agent actions. Kernel exposes a REST API (OpenAPI 3.1, 135 operations across 22 tags), first-party TypeScript, Python and Go SDKs, a CLI, and a centrally hosted MCP server so agents can drive real browsers. Backed by General Catalyst.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Kernel the way a machine reads it — 30 machine-readable artifacts across 22 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Kernel scores 54.4/100 (developing), with a separate agent-readiness read of 69/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Kernel
Each block below is one kind of artifact we hold for Kernel. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 22
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Kernel API Keys API
Create and manage API keys for organization and project-scoped access.
Kernel Apps API
List applications and versions.
Kernel Audit Logs API
Read audit log records for the authenticated organization.
Kernel Browser Computer Controls API
Control mouse, keyboard, and screen on the browser instance.
Kernel Browser Filesystem API
Read, write, and manage files on the browser instance.
Kernel Browser Logs API
Stream logs from the browser instance.
Kernel Browser Playwright API
Execute Playwright code against the browser instance.
Kernel Browser Pools API
Create and manage browser pools for acquiring and releasing browsers.
Kernel Browser Processes API
Execute and manage processes on the browser instance.
Kernel Browser Replays API
Record and manage browser session video replays.
Kernel Browser Telemetry API
Stream live telemetry events from a browser session.
Kernel Browsers API
Create and manage browser sessions.
Kernel Credential Providers API
Configure external credential providers like 1Password.
Kernel Credentials API
Create and manage credentials for authentication.
Kernel Deployments API
Create and manage app deployments and stream deployment events.
Kernel Extensions API
Create, list, retrieve, and delete browser extensions.
Kernel Invocations API
Invoke actions and stream or query invocation status and events.
Kernel Managed Auth API
Create and manage auth connections for automated credential capture and login.
Kernel Organization API
Read and manage organization-level limits.
Kernel Profiles API
Create, list, retrieve, and delete browser profiles.
Kernel Projects API
Create and manage projects for resource isolation within an organization.
Kernel Proxies API
Create and manage proxy configurations for routing browser traffic.
Scroll within the panel for all 22 ·
Arazzo Workflows 2
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZOKernel - create a browser, run Playwright, screenshot, tear down
End-to-end cloud browser automation on Kernel.
ARAZZOMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
kernel-mcp.yml
MCP SERVERSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Kernel — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/kernel · machine-readable index on apis.io