Give your agent eyes, and an eraser
Your AI agent writes code, searches the web, and manages files. Give it image editing too. Peelaway exposes REST and MCP interfaces, with machine-readable discovery for automated workflows.
Drop your image here
or click to browse. PNG, JPG up to 20MB
Built for autonomous workflows
Three machine-readable discovery formats plus REST and MCP integration paths.
SKILL.md: agent skill definition
A structured skill file that tells coding agents exactly how to use Peelaway: when to invoke it, the 3-step workflow, request/response formats, and error handling. Drop it into Claude Code, Cline, or any agent that supports skill files.
llms.txt: LLM-readable service description
A plain-text service overview optimized for LLM consumption. Describes what Peelaway does, lists all endpoints, and links to the OpenAPI spec. Discoverable at /llms.txt.
OpenAPI 3.1 contract
The machine-readable contract at /openapi.json defines the current REST paths, authentication, request bodies, responses, and webhook callback.
Three-endpoint async API
Submit with POST /api/process, poll with GET /api/process/status, then fetch a signed image URL from GET /api/process/result.
JSON request, signed-URL result
Send base64-encoded input image bytes and a prompt in JSON. A completed result response contains a signed URL for downloading the output image.
Polling or signed webhooks
Poll until a job reaches done or error, or include a public HTTPS webhook_url and verify the signed terminal callback.
A contract agents can inspect
Peelaway exposes the same asynchronous image-editing workflow through REST and MCP. REST requests send base64-encoded image bytes in JSON, then receive a job ID. Agents can poll the job and fetch a signed result URL, or provide a webhook URL for a signed callback.
Machine-readable discovery lives at /openapi.json, /SKILL.md, and /llms.txt.
REST calls accept a pk_ bearer key in the Authorization header. MCP clients can use the same key or the advertised OAuth 2.1 flow.
Status responses use pending, done, or error. The discovery guide recommends polling every 2–5 seconds while a job is pending.
When status is done, GET /api/process/result returns job metadata and a signed image URL that is valid for one hour.
The OpenAPI contract documents validation, authentication, credit, rate-limit, pending, unknown-job, and processing-failure responses.
Frequently asked questions
Peelaway for other industries
Integrate through REST or MCP
HTTP-capable agents can use the REST contract. MCP clients can connect when they support Peelaway's transport and authentication options.
Coding Agents & AI IDEs
Agent Frameworks
MCP-Compatible Clients
LLM Providers & Platforms
Automation & Workflow
Agent integration workflow
Discover the OpenAPI 3.1 contract, submit a complete request, poll while pending, then fetch the signed result URL.
# LLM-readable overview
curl https://api.peelaway.io/llms.txt
# Structured skill definition
curl https://api.peelaway.io/SKILL.md
# Machine-readable spec
curl https://api.peelaway.io/openapi.json# Submit
curl -X POST https://api.peelaway.io/api/process \
-H "Authorization: Bearer $PEELAWAY_KEY" \
-H "Content-Type: application/json" \
-d '{"image":"<base64>","prompt":"remove the sign"}'
# → {"job_id":"8f4a17000e17a1b2c3d4e5f607182930","credits_remaining":24}
# Poll
curl -H "Authorization: Bearer $PEELAWAY_KEY" \
"https://api.peelaway.io/api/process/status?job_id=8f4a17000e17a1b2c3d4e5f607182930"
# → {"status":"done","width":4000,"height":3000,"format":"jpeg","credits_used":1,"credits_remaining":24,"processing_time_ms":8420}
# Fetch the signed result URL
curl -H "Authorization: Bearer $PEELAWAY_KEY" \
"https://api.peelaway.io/api/process/result?job_id=8f4a17000e17a1b2c3d4e5f607182930"
# → {"job_id":"8f4a17000e17a1b2c3d4e5f607182930","url":"https://.../signed-url","format":"jpeg","width":4000,"height":3000,"credits_used":1,"credits_remaining":24,"processing_time_ms":8420}