> ## 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.

# Runs

> See every call you made, what it cost, how long it took and which requests it sent to the site.

Peel keeps a record of every call to your APIs and to the marketplace: the endpoint, whether it succeeded, the site's status code, how long it took, what it was charged, and the requests it sent to the site. Open **Runs** in the app, or read them over REST and MCP.

## List runs

```bash theme={null}
curl "https://api.peel.sh/v1/runs?limit=25" -H "X-API-Key: $PEEL_API_KEY"
```

```json theme={null}
{
  "runs": [
    {
      "id": "jh751rparxh4e7nfc3vk23vd618jdhhh",
      "api_id": null,
      "marketplace_id": "kd7cw9zbzvsgxgywa0m9mhac298jd4rg",
      "endpoint": "search_packages",
      "status": "success",
      "status_code": 200,
      "error_code": null,
      "duration_ms": 3181,
      "credits_charged": 0,
      "transport": "html_browser",
      "request_id": "co40gta50zb2xtda4md7",
      "actor": { "type": "api_key", "user_id": "kd71x0m4c2t9r8s6v5w3y1z7ab4q2e8f", "key_id": "Lw4mT0xQe2Rk9sVb" },
      "created_at": "2026-11-17T05:22:34.666Z"
    }
  ],
  "next_cursor": "…"
}
```

This run searched Go packages from the marketplace on an unlimited plan, so it was charged 0. `actor` says who made the call: a signed-in person (`session`, with `user_id` and `email`), a key (`api_key`, with `key_id`) or an MCP client (`bearer`). It is `null` on runs made before November 17, 2026.

Runs come newest first. Pass `api_id` to see one API's runs, `limit` for 1 to 100 per page (25 by default), and `next_cursor` as `cursor` to get the next page. `next_cursor` is `null` on the last page.

## One run and its requests

`GET /v1/runs/{run_id}` returns the run with `requests`: the method, origin, path and status code of each request the run sent, in order, up to 32. Static files such as images, stylesheets, scripts and fonts are left out. Query strings are dropped, and any value you passed in the call's input is replaced with `…` in the path, so the log does not keep what you searched for or who you looked up.

A run that is not yours, or does not exist, is 404 `run_not_found`.

## From an MCP client

The Peel MCP lists `list_runs` and `get_run`. Both need `mcp:read`; an API key needs `apis:read`.


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