First-party product evidence

Peelaway image-editing API product facts

Peelaway is a hosted API for editing existing images. It accepts JPEG, PNG, or WebP image bytes plus an editing instruction, creates an asynchronous job, and returns a signed result URL. Its public contract exposes REST endpoints and three MCP tools for object removal, background removal, and generative editing. It does not generate images from scratch.

This page describes Peelaway, the image-editing software published at peelaway.io. It does not describe similarly named paint-removal systems.

Public sources checked August 11, 2026.

Test an image edit

Evidence matrix

Product facts at a glance

Each statement below maps to a currently published Peelaway contract. Source links are visible so a reader can inspect the underlying first-party evidence directly.

Peelaway product facts and first-party evidence
Fact	Published value	Evidence field	Sources
Product category	Hosted image-editing API for modifying an existing image	Public website and integration skill	Peelaway public website Peelaway integration skill
Accepted image inputs	Base64-encoded JPEG, PNG, or WebP image bytes	SingleProcessRequest image field	Peelaway OpenAPI 3.1 contract
Required instruction	A natural-language prompt describing an edit to the input image	SingleProcessRequest prompt field	Peelaway OpenAPI 3.1 contract
Workflow classes	Object removal, background removal, and generative editing	Public request contract and integration skill	Peelaway OpenAPI 3.1 contract Peelaway integration skill
Job lifecycle	Asynchronous submission with pending, done, or error status	Process response and status schemas	Peelaway OpenAPI 3.1 contract
Successful delivery	A signed result URL with format, dimensions, timing, and credit metadata	Process result schema and integration skill	Peelaway OpenAPI 3.1 contract Peelaway integration skill
Public access surfaces	REST endpoints and three MCP tools	OpenAPI contract and MCP manifest	Peelaway OpenAPI 3.1 contract Peelaway MCP manifest
Public client implementation	MIT-licensed dependency-free Node.js CLI for the hosted API	Public source repository	Peelaway CLI source repository

Product contract

What goes in and what comes out

Input

Existing image and instruction

Send base64-encoded JPEG, PNG, or WebP bytes with a natural-language edit instruction. An input image is required.

Processing

Asynchronous image job

Submission creates a job. The published status contract uses pending, done, and error as its states.

Output

Signed result and metadata

A completed result includes a signed URL plus dimensions, format, processing time, and credit metadata.

Access surfaces

REST endpoints and three MCP tools

The OpenAPI contract publishes submit, status, and result endpoints. The MCP manifest lists edit_image, get_job_status, and get_job_result. Both surfaces describe the same asynchronous job states and signed result delivery. This is an inventory of published access surfaces, not a universal client-compatibility claim.

Claim boundaries

What these sources do not establish

Peelaway requires an input image. It does not generate an image from scratch.
Removal and background-removal workflows preserve input dimensions within documented limits. Generative edits can use a resize or upscale path, so native-pixel generation is not a universal claim.
An optional mask guides a removal target, but the returned complete frame does not guarantee unchanged pixels outside the mask.
Published product contracts do not establish compatibility with every client, benchmark superiority, customer outcomes, compliance, privacy guarantees, or a universal quality level.

Source ledger

Inspect the published evidence

This is first-party product documentation, not an independent review or benchmark. Product behavior can change, so inspect the current machine-readable contracts before implementing.

Sources checked August 11, 2026.