> ## Documentation Index
> Fetch the complete documentation index at: https://docs.peel.sh/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Peel builds APIs from a URL and a task. Use only the REST routes under https://api.peel.sh and the hosted MCP server at https://api.peel.sh/mcp. Authenticate with the X-API-Key header, or send the same key as Authorization: Bearer. Errors carry code, message, retryable, retry, docs_url and details; branch on code. The peel CLI and the open-source SDK are not published; do not run npm install peel, which is an unrelated package. The keyless routes need no key and no session: the GET /public/marketplace routes, POST /v1/marketplace/{marketplace_id}/endpoints/{endpoint_name}:call and https://api.peel.sh/mcp/keyless. Account routes take a key or a signed-in session and answer 401 without one. These take only a session from peel.sh and refuse a key: GET /v1/accounts, POST /v1/accounts/join, POST /v1/accounts/{account_id}/leave, POST /v1/team/invites, GET /v1/connected-apps, DELETE /v1/connected-apps/{client_id}, PUT /v1/logins, DELETE /v1/logins, GET /v1/logins/code and the /account/billing routes. Every route with its schemas is in https://docs.peel.sh/openapi.json. Use the exact route, field and error-code names shown in these pages, and read the API Reference tab for request and response schemas.

# Changelog

> What changed in Peel, newest first.

**20 November 2026**

Easier first steps for agents, and unpublish

* **Fresh-agent check: 8 of 8 tasks, 4 and 6 stalls.** Before each docs release, a coding agent with no account, no key and no source code is given only peel.sh, docs.peel.sh and api.peel.sh and eight tasks: a REST call and an MCP call without a key, fixing a bad input from its error, building an API from a URL, paging, the CLI, webhooks and schedules, and pricing. Two runs on 20 November passed all eight; a stall is a request that failed or answered an error.
* **The API host explains itself.** `GET https://api.peel.sh/` answers a JSON index with the docs, the OpenAPI spec and the routes that work without a key, and the spec path on the API host leads to [the OpenAPI spec](https://docs.peel.sh/openapi.json). Browsers still go to peel.sh.
* **A path with no route answers `404`.** It used to ask for a key. The message names the route list.
* **Unpublish from the marketplace.** `POST /v1/apis/{api_id}/marketplace/unpublish`, `peel marketplace unpublish` and the MCP tool `unpublish_api_from_marketplace` take your listing down. Calls to it answer `404` `marketplace_api_removed` and charge nothing; your API keeps working, and publishing again restores the same listing. See [Marketplace](https://docs.peel.sh/features/marketplace.md#unpublish-your-api).

**17 November 2026**

Sign-in, versions and account

* **Schedules.** Run a read endpoint every hour, day or week with fixed input. When its answer changes, Peel sends `schedule.changed` with the new data. See [Schedules](https://docs.peel.sh/features/schedules.md).
* **Sessions renew themselves.** When a read's session has expired and a saved login covers the site, Peel signs in once and runs the read again. The answer carries `session_renewed: true` and the new session. See [Authenticated APIs](https://docs.peel.sh/features/authenticated-apis.md#when-the-session-expires).
* **Import logins.** The **Logins** page reads a password manager's CSV export in your browser and saves only the logins you pick.
* **Status page.** [peel.sh/status](https://peel.sh/status) shows whether the API and the website are up, checked every 5 minutes from outside Peel's servers.
* **Connected apps.** **Settings** lists the OAuth apps you approved, such as Claude or Cursor, and disconnects them. See [Authentication](https://docs.peel.sh/getting-started/authentication.md).
* **Drafts and version pinning.** Revise or rebuild with `draft: true` to build a version that does not go live. Call it with the `Peel-Version` header, then publish it. `GET /v1/apis/{api_id}/code` shows what each endpoint runs. See [API updates](https://docs.peel.sh/features/api-updates.md).
* **Teams and an audit log.** Invite people as admin, member or tool user; switch between accounts in **Settings**; read who changed what with `GET /v1/audit-events`. See [Teams](https://docs.peel.sh/features/teams.md).
* **Keys API.** List, create, rotate, rename and revoke API keys over REST, with an expiry of 1 to 365 days.
* **Quota.** `GET /v1/quota`, a daily run cap, usage alert emails and a monthly summary. Running out answers `429` with `quota_exceeded` and `Retry-After`.
* **Repair inside the call.** A call that fails because the site changed starts a repair at once and answers `api_repairing`.
* **Runs.** Every call, batch and execution is listed in **Runs**, with the requests it sent.
* **Wrong-data checks.** A build no longer publishes clock times without a zone, or an empty list where the site answered an error or showed a count.

**16 November 2026**

Try it, batches and shapes

* **Try without an account.** Public marketplace endpoints answer REST and MCP calls without a key, up to 25 a day per address. See [Marketplace](https://docs.peel.sh/features/marketplace.md).
* **Batches.** Run a read endpoint on 1 to 100 inputs in one call. See [Batches](https://docs.peel.sh/features/batches.md).
* **Shapes.** Pick, rename, filter, sort and group a call's rows with a JSON shape. See [Shapes](https://docs.peel.sh/features/shapes.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.