Two phases
Build pipeline
1
Admit
POST /v1/apis checks your build allowance and your build-queue limit, reserves the build and queues it. A compatible existing API is returned with matched: true and no charge.2
Investigate
The compiler reads public pages, captures network requests and inspects browser behavior to find the requests or page steps that produce the data you asked for.
3
Compile
It writes one JavaScript program per endpoint, together with input and output schemas, declared examples, the network origins the program may reach, and links to the evidence it relied on. A write also declares the postconditions that prove its effect.
4
Verify
Peel runs every declared example against the exact program through the same executor customers use. A browser read with inputs must return different results for two different inputs, and each first-page example must pass a second time, so a program that reads a page before it finishes loading does not publish. Other programs are checked by replaying their recorded sources reordered, perturbed and emptied, which catches canned or constant output. Every example’s output must also pass three data rules: each date and time carries its zone offset (
2026-11-17T09:30:00-05:00, or Z for UTC; plain dates stay YYYY-MM-DD); an empty list is refused when a source the program read answered an error, because a site’s error page is not “no results”; and an empty list is refused when the same object counts results, such as total: 12.An independent reviewer checks each step before it runs and the results before publication. It follows OpenAI Codex’s Guardian policy, adapted for website builds: it rates each step’s risk and how far your task authorizes it, and Peel blocks a step with critical risk, or with high risk that your task does not clearly authorize. Failed checks go back to the same compiler for bounded repair. Any change to the program invalidates its verification.5
Publish
One atomic step publishes an immutable version, and only a version that passed verification is published. If nothing passes, the build ends as
failed and keeps structured diagnostics.What a build publishes
GET /v1/apis/{api_id} returns the contract for the current version:
REST
:call, the MCP call_endpoint tool and the exports all read this same stored version.
Live build questions
A build can pause and ask you something while it keeps its browser and history alive: a clarification, a private value such as a password, or confirmation of a write. Answer throughPOST /v1/apis/{api_id}/respond with question_id and answer, through the MCP respond_to_api_input tool, or in the dashboard. See Answer a build question. Private answers stay on Peel’s server, and only their names reach the build model.
When a build fails
A failed build is a result, not a hidden fallback.api.failure carries a compact code, the category, a message, a recommended action, whether a retry can help, the technical reason and a support_debug_id. Peel never publishes an endpoint it could not verify. The catalog is in Errors.
Quality bar
A published endpoint must return the requested data, use real parameters, advance pagination, return valid empty results and report errors truthfully. Status codes alone, echoed inputs and optimistic flags do not count as proof.Changing and refreshing
Userevise to change instructions and rebuild to recompile from fresh evidence. Both publish a new version under the same api.id. See API updates.