Kernel SOP

Appearance

Test ​

Status: PASS (HTTP 200 confirmed on Hetzner 2026-07-01) ​

The Kernel API is live and responding. The endpoint moved from the old api.kernel.sh domain to api.onkernel.com. A KERNEL_API_KEY is present in MASTER_API_KEYS.env and authenticated successfully.

Hetzner (server) ​

Verify command (run on agent-runtime-hetzner-1):

bash
ssh -o BatchMode=yes -o ConnectTimeout=15 agent-runtime-hetzner-1 \
  'source ~/fleet.env; curl -s -o /dev/null -w "kernel(onkernel) HTTP %{http_code}" \
  -H "Authorization: Bearer $KERNEL_API_KEY" https://api.onkernel.com/browsers'

Real output:

kernel(onkernel) HTTP 200

Date verified: 2026-07-01

Status: PASS. The API authenticated and returned HTTP 200.

What was previously attempted (now historical) ​

bash
curl -s "https://api.kernel.sh/v1/sessions" -H "Authorization: Bearer $KERNEL_API_KEY"

Previous output:

Could not resolve host: api.kernel.sh

DNS resolution failed for api.kernel.sh. The domain migrated to api.onkernel.com.

Correct API base URL ​

https://api.onkernel.com (not api.kernel.sh)

What is required to use Kernel ​

  • A valid Kernel account and API key (KERNEL_API_KEY in MASTER_API_KEYS.env)
  • Use base URL: https://api.onkernel.com
  • No local install needed; Kernel is a cloud browser API
  • SDK: @onkernel/sdk npm package pointed at https://api.onkernel.com

How to verify ​

bash
source ~/fleet.env
curl -s -o /dev/null -w "HTTP %{http_code}" \
  -H "Authorization: Bearer $KERNEL_API_KEY" \
  https://api.onkernel.com/browsers

A 200 response confirms the API key is valid and the endpoint is live.