Skip to main content
Give Peel a URL and a job. Build-time agents inspect public pages, network traffic, selectors, and official surfaces, then Peel publishes named endpoints only when the result passes evidence, schema, runtime, and policy gates. The result is a reusable API surface for apps and agents: REST endpoints, OpenAPI exports, MCP tools, and a first-party CLI. Runtime calls execute the stored contract. They do not launch a browser, call a model, or rediscover the site on every request.
Peel is currently in private preview. Public signup is disabled on peel.sh, so use an existing account and API key from https://peel.sh/settings.

​
Start here

Quickstart

Build, inspect, and call your first compiled API.

CLI

Set up the hosted CLI, auth flow, and MCP install path.

How it works

See the build-time agent and deterministic runtime model.

Authentication

API keys and OAuth for REST and MCP clients.

Core concepts

APIs, endpoints, matching, and sessions.

​
Core operations

The public API surface centers on build, runtime, lifecycle, diagnostics, and export operations: Every operation on an existing API keeps the same api.id, so callers and generated clients do not need to migrate after updates.

​
Base URL

All REST API requests go to this host. The MCP server is at https://api.peel.sh/mcp. Every build returns an api.id, which is the stable handle for later operations. If you call POST /v1/apis with a URL that already has a compatible build, Peel reuses it (matched: true). Pass force_new: true to compile a fresh one. The CLI defaults to the same API host for programmatic calls and opens browser auth on https://peel.sh when needed. See CLI.