Keres for Developers — automation API, MCP, Playwright, CLI

MCP gateway

Agents drive profiles through safe tools.

MCP is an interface layer over the Keres automation API — never a backdoor into the runtime. Every tool is permission-checked, and sensitive data (cookies, tokens, passwords) never leaves unless explicitly authorized.

Profile tools: list, create, launch, stop — agents work inside the profiles you allow.
Browser tools: navigate, click, type, fill, scroll, snapshot, screenshot, evaluate.
Session tools: list, attach, close — with per-agent permission boundaries.

One session, three calls

Stable tool names and versioned schemas.

launch_profile({ profile: "research" })
navigate({ url: "https://example.com/pricing" })
snapshot() → structured content, ready to reason over

Automation API

One API. Two engines. No CDP in your code.

Your code talks to the Keres automation abstraction; engine adapters translate to CDP on Chromium and WebDriver BiDi on Gecko. Swap engines per profile without touching your scripts.

navigate · snapshot

Load pages and read structured content — no screenshot-parsing required.

click · fill · type · select

Human-grade interaction primitives with waits built in.

scroll · screenshot

Move through long pages; capture proof with every run.

wait · evaluate

Synchronize on conditions; run JavaScript where only JS will do.

recordings → replays

Capture once in the UI, replay exactly from code — LLM-free and deterministic.

schedules

Daily, weekly, interval, once — with retries, catch-up, and full history.

camoufox profile

Hardened Firefox-based runtime per profile: coherent screen, fonts, canvas, media, and timezone with zero configuration.

Interoperability

Plays well with the tools you already use.

Keres complements the ecosystem instead of trapping you in a proprietary model.

Playwright-compatible. Point existing scripts at Keres runtimes instead of stock browsers.
CDP + WebDriver BiDi under the hood, exposed as developer access when you need the raw protocols.
Versioned, documented decisions — engine updates are tested against automation, profiles, and runtime before they ship.

Script everything from the CLI

Resources, actions, JSON output, dry runs, honest exit codes.

$ profile, task, schedule, recording — one grammar
keres profile launch research
keres task run price-watch --output json
keres schedule list --output table
keres help automation

Script the browser. Keep the profiles.

Agents drive profiles through safe tools.

One session, three calls

One API. Two engines. No CDP in your code.

Plays well with the tools you already use.

Script everything from the CLI

Build on the browser runtime that respects isolation.