First-party product evidence

Peelaway Image API facts

Peelaway turns photos into paintings, illustrations and posters with curated styles, including watercolor portraits and playful pet artwork. Create with a photo, an idea, or both. Moments turns one photo into a short clip with sound. Fashion Shot, Image Edit, YouTube Thumbnail, and browser utilities are specialized Tools. The Image API and MCP provide image-editing access for integrations and compatible AI assistants.

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

Public sources checked September 11, 2026.

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
FactPublished valueEvidence fieldSources
Product categoryImage generation and image editing with curated visual stylesPublic website and product pagesPeelaway public website
Image API inputsBase64-encoded JPEG, PNG, or WebP image bytesSingleProcessRequest image fieldPeelaway OpenAPI 3.1 contract
Image API instructionA natural-language prompt describing an edit to the input imageSingleProcessRequest prompt fieldPeelaway OpenAPI 3.1 contract
Image API workflowsObject removal, background removal, and generative editingPublic request contract and integration skillPeelaway OpenAPI 3.1 contractPeelaway integration skill
Job lifecycleAsynchronous submission with pending, done, or error statusProcess response and status schemasPeelaway OpenAPI 3.1 contract
Successful deliveryA signed result URL with format, dimensions, timing, and credit metadataProcess result schema and integration skillPeelaway OpenAPI 3.1 contractPeelaway integration skill
Public access surfacesGallery creation, Fashion Shot, Image Edit, YouTube Thumbnail, browser utilities, Image API, and MCPPublic website, OpenAPI contract, and MCP manifestPeelaway public websitePeelaway OpenAPI 3.1 contractPeelaway MCP manifest
Public client implementationMIT-licensed dependency-free Node.js CLI for the Image APIPublic source repositoryPeelaway CLI source repository

Product contract

What goes in and what comes out

Input

Image API: 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

Image API endpoints and MCP tools

The OpenAPI contract publishes Image API submit, status, and result endpoints. The MCP manifest lists edit_image, get_job_status, get_job_result, and share_image. 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

  • The Image API and MCP editing tools require an existing image. The Peelaway web app also generates images from a prompt, with or without a reference photo.
  • 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.
  • The public Image API does not accept a mask parameter. Describe the target in the prompt; generative editing does not guarantee unchanged pixels outside the requested change.
  • 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 September 11, 2026.