Browse and search
The browse routes need no authentication.Cache-Control is public, max-age=N, stale-while-revalidate=60, where N is 15 minus the age of Peel’s copy, so through a browser or a shared cache a browse answer can be up to 75 seconds old: 15 seconds fresh, then up to 60 more while it revalidates. A 404 is not cached.
A summary has id, name, description, source_host, source_url, endpoint_count, requires_session and updated_at. Pass next_cursor as cursor for the next page. The id is the marketplace_id used below. Over MCP, use list_marketplace_apis, get_marketplace_api and search_marketplace_endpoints.
Each endpoint in the detail has the same fields as an endpoint of your own API: endpoint_name, input_schema, output_schema, credit_cost and examples. An endpoint you can call directly carries one example with the request, a curl line, the peel marketplace call command and the MCP call_marketplace_endpoint arguments; it runs as is, without an account. Other endpoints have empty examples: install the API to call them.
Call a public endpoint directly
POST /v1/marketplace/{marketplace_id}/endpoints/{endpoint_name}:call runs an endpoint from the canonical marketplace version. It works only for public data endpoints on APIs that need no session.
Idempotency-Key is not billed again: it replays the first response, marked Idempotent-Replayed: true, only when that call succeeded and its response was stored (up to 375 KB). Otherwise the retry answers 409 with the recorded outcome. Any other endpoint returns 409 with code: "marketplace_direct_call_not_allowed". Install the API to use it fully.
Call without an account
The same call works with no key at all, so you can try an API before you have an account.- Each address gets 25 calls a day, and all calls without an account share 2,000 a day. Both reset at midnight UTC. Past either one the answer is
429withcode: "try_limit_reached"andRetry-Afterset to the seconds until midnight UTC. - Only public data endpoints. Anything signed in, a sign-in, or an action answers
401withcode: "sign_in_required". Idempotency-Keyand session headers are ignored. Nothing is stored for you: no run history and no charge, so the answer has nocredits_chargedorcredits_remaining.- Every call runs live against the site. Peel does not cache call answers.
- Every answer carries a
noticesaying what an account adds; on a refusal it isdetails.notice. - An unknown endpoint answers
404withdetails.available_endpoints.
Files and outages
- An endpoint that saves or reads a file answers
409withcode: "not_executable"without an account, before it runs. A file save attempted while running fails the call witherror_code: "files_need_account". Install the API to use files. - When Peel cannot check the daily limits within 250 milliseconds, the answer is
503withcode: "temporarily_unavailable"andRetry-After: 30. Calls with a key are not affected.
https://api.peel.sh/mcp/keyless. It offers list_marketplace_apis, get_marketplace_api, search_marketplace_endpoints and call_marketplace_endpoint under the same limits; a limit comes back as a tool error with retry_after_seconds. It takes no key: one sent there answers 400 with code: "keyless_url_credentials", and keyed clients use https://api.peel.sh/mcp.
Install an API
POST /v1/marketplace/{marketplace_id}/install copies a marketplace API into your account as a private API.
api_id with every route in the API Reference. An unknown marketplace_id returns 404.
Publish your API
POST /v1/apis/{api_id}/marketplace/publish publishes the current version of an API you own, or contributes it back to an existing canonical API.
expected_marketplace_version_id with the canonical version you based your work on. It is a compare-and-swap value: the contribution fails if the canonical version has moved. The response includes published, already_published, publication_kind (first_publish or contribution), marketplace_id, api_id, version_id, source_version_id and visibility (global). A first publish returns 201 and a repeat returns 200. Other users cannot see your APIs unless you publish one.
Unpublish your API
POST /v1/apis/{api_id}/marketplace/unpublish takes your API’s listing off the marketplace. The CLI command is peel marketplace unpublish <api-id> and the MCP tool is unpublish_api_from_marketplace.
200 with unpublished, already_unpublished, marketplace_id, api_id and version_id. Repeating the call, or calling it for an API you never published, answers 200 with already_unpublished: true.
After you unpublish:
- The listing leaves marketplace list, search and detail. Those reads are cached for up to 15 seconds, and a cache in front of Peel may serve the old answer for 60 seconds more while it refreshes.
- Calls to the
marketplace_id, with or without a key, answer404marketplace_api_removedand charge nothing. This includes saved MCP setups and scripts that call it. - A call that was already running when you unpublished may still finish and be charged; nothing new starts.
- Your API and its own routes keep working. Private copies other users installed keep working too, because each is the installer’s own API.
- The listing page and the sitemap on peel.sh are built when the website is deployed, so the page stays in the static files until the next deploy. A visitor’s browser loads the listing again when the page opens and shows “not found”.
marketplace_id. After a rebuild you do not need expected_marketplace_version_id for this; sending the listing’s current version works too. Only the API that unpublished the listing can list it again. A listing Peel removed, for example after a site owner’s request, cannot be published again and answers 409 marketplace_listing_removed. When a publisher deletes its API, its listing goes off the marketplace until another contributor publishes a newer version to it.
Only the API that last published the listing can unpublish it. An installed copy, or an API whose contribution someone else replaced, gets 409 marketplace_not_publisher. On a team, anyone whose role can publish (admin or member) can also unpublish.
Installed copies
An installed API is your own copy of the marketplace version at the time you installed it. It does not change when the marketplace version changes, and installing again returns the same copy. Revise, rebuild, repair and roll it back like any API you built; see API updates. Calls throughPOST /v1/marketplace/{marketplace_id}/endpoints/{endpoint_name}:call always use the current marketplace version.