Skip to content
cutstack
Start free
Agents & APINot available yet

Plug in your agent. Get back the batch.

Cutstack is a web app today. This is how the agent and developer version would work: the same studio, driven by an MCP tool call or a REST request. The form at the bottom decides whether we build it.

Tell us what you’d build

The loop, in three steps

run the spring drop197 clean · 3 flagged · 3 refundedMCP200 photosZIPYour agentCutstackBatch, checkedback to the agent as a ZIP

  1. Your agent sends the batch

    Over MCP from Claude, GPT or any MCP client, or from your own code over the API. Up to 200 photos: files, links or a ZIP.

  2. Cutstack cuts and checks

    The same AI model and the same automatic check as the studio. A broken result is flagged and its credit comes back.

  3. The ZIP comes back

    Sized for the marketplace and named your way, with a short list of the photos worth a second look.

How it would work

One engine, two doors. Everything the studio does, the API does with the same logic. The MCP server is that API dressed as tools, so an agent can drive it without a line of code.

For agents

MCP server

Your agent gets Cutstack as a set of tools. The server runs next to it on your machine, starts with your API key and works in Claude Desktop, Cursor and Claude Code with no extra sign-in.

  • Images never enter the chat. Tools pass IDs and links and answer in summaries: 197 clean, 3 to check, and why. The files travel over HTTPS, outside the conversation.

  • The agent only looks at what is flagged. One tool returns the flagged photos with the reason and the area. A small thumbnail comes along only when the agent asks for it.

  • Credits are never a surprise. Every tool that spends a credit says so in its description and in its answer.

agent ⇄ cutstackconcept
  1. agent

    Process the 200 photos in /drops/spring for Amazon.

  2. cutstack

    create_job, add_images

    200 photos · preset amazon-main · white

  3. cutstack

    start_job, wait_job

    197 clean · 3 flagged · 3 credits returned

  4. agent

    Show me the three.

  5. cutstack

    review_queue

    3 photos · reason and area for each

  6. agent

    Retry #12, drop the other two, export as {sku}.jpg.

  7. cutstack

    retry_item, delete_items, export_zip

    spring-amazon.zip · 198 photos · ready

For your code

REST API

Plain HTTPS with a secret key, shown once when you create it. The same batch the studio runs, one request per step.

  • One photo, one call. For a single image there is a shortcut: send the photo, get the cutout back within a minute.

  • Events instead of polling. Live progress as a stream, or signed webhooks when a photo is done, a photo is flagged or the batch finishes.

  • Safe to retry. Every request that creates or charges carries an idempotency key, so a network retry never charges twice.

/v1concept
  1. POST

    /v1/jobs

    Create a batch with its preset and background

  2. POST

    /v1/jobs/{id}/items

    Add files, links or a ZIP

  3. POST

    /v1/jobs/{id}/start

    Run it, or try 10 photos first

  4. GET

    /v1/jobs/{id}/review

    Only the flagged photos, with the reason

  5. GET

    /v1/jobs/{id}/download

    The ZIP, named your way

Same credits, same refunds, same rules

Whatever runs the batch, a person or an agent gets the same promise.

credit per photo that comes out clean
1
credits for a broken result
0
photos per batch
200
then the batch is deleted
~2 h

Nothing here is a promise of a date; it is the shape of what we would ship, and the form below decides whether we do.

Your use case

We read every one. When we build it, you hear first.

Where the photos come from, where the cutouts go, what runs in between.

Used only to reply about the API. Nothing else, no list.