What runs on a call
Each endpoint is one async JavaScript function that Peel compiled and verified at build time. A call runs that exact function:- The host checks your API key, run allowance and rate limit, and validates your parameters against
input_schema. - The host starts an owned worker process. The program runs inside a QuickJS sandbox in that process.
- The program reaches the site only through the capabilities its endpoint declared.
- The host checks the result against
output_schemaand returns the standard envelope.
Capabilities a program can declare
Limits
- The sandbox has no Node, no filesystem, no environment variables, no cookies and no raw browser control.
- Requests are limited to declared origins. The host checks destinations, DNS and every redirect, and refuses private and metadata addresses.
- Time, memory, request count and output size are bounded for each execution. Cancelling or timing out kills the worker.
- Secrets and session state belong to the host. They never enter the program, a model prompt or a saved program.
What a saved call never does
Reads and writes
A read endpoint returns data. A write endpoint (endpoint_type: "guided_action") changes something on the site, so it runs only after you confirm the exact operation, input and outbound requests. Peel records a durable claim before sending, and confirming twice returns the first result instead of sending again. Details are in Signed-in and action endpoints.
When the site changes
A published version does not change. If the site changes and calls start failing,GET /v1/apis/{api_id}/health shows it and POST /v1/apis/{api_id}/rebuild compiles a new version from fresh evidence. See API updates.