MegaPotato API

Create a key on your account page, put it in the MEGAPOTATO_API_KEY environment variable, and run:

# 1. Send a photo
curl https://megapotato.app/v1/upscale \
  -H "Authorization: Bearer $MEGAPOTATO_API_KEY" \
  -H "Idempotency-Key: photo-001" \
  -F [email protected] \
  -F upscale=4
# → {"id": "6f6f4c1e-…", "status": "queued", "upscale": 4, "cost_chips": 8}

# 2. Wait for it (the server holds the request up to 55 s)
curl "https://megapotato.app/v1/jobs/6f6f4c1e-…?wait=55" \
  -H "Authorization: Bearer $MEGAPOTATO_API_KEY"
# → {"status": "completed", "result_url": "https://…", …}

Want to wire things up before buying chips? Any signed-in account can create a test key (mp_test_…) on the account page. It goes through the whole flow — uploads are checked and priced exactly like with a live key — but nothing runs and nothing is charged: every job comes back completed with a sample image. A retry with the same Idempotency-Key and photo returns the same job id; reusing a key for a different photo is only rejected (422) on live keys. Switch to a live key when you're ready; live keys unlock with your first chip pack.

Send your key on every request in the Authorization header: Bearer mp_live_…. Keys are shown once when you create them; we store only a hash. Keep them on your server — never in a mobile app, a web page or a repository. If a key leaks, revoke it on your account page; it stops working immediately.

Send the input size and factor, get the price back. Nothing is uploaded or charged.

curl https://megapotato.app/v1/quote \
  -H "Authorization: Bearer $MEGAPOTATO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"width": 4000, "height": 3000, "upscale": 2}'
# → {"cost_chips": 21, "output_width": 8000, "output_height": 6000, "upscale": 2}

Multipart form with file (PNG, JPG, WEBP and HEIC, up to 40 MB) and upscale: 1 (refine, same size), 2, 4 or 8. The input can be up to 6 000 px on its long edge, and the result up to 16 400 px — pick a smaller factor for large photos.

{"id": "6f6f4c1e-…", "status": "queued", "upscale": 4, "cost_chips": 8}

cost_chips is held from your balance right away and charged when the photo is done. If processing fails, the chips come back automatically.

Add ?wait=55 and the server holds the request until the job finishes or 55 seconds pass, whichever comes first — one call usually covers the whole job.

Most photos are back in seconds. When demand grows we bring more capacity online, and the first requests after that can take a couple of minutes — then everything runs at full speed. Keep polling with ?wait=55; there's nothing special to handle.

{
  "id": "6f6f4c1e-…",
  "status": "completed",          // queued → running → completed | failed
  "result_url": "https://…",      // PNG; a link valid for about an hour, no auth header needed
  "error": null,                  // the reason when failed, with "your chips were refunded"
  "upscale": 4,
  "created_at": "2026-09-15T10:00:00Z",
  "eta_seconds": null             // an estimate while queued or running
}

Fetch the job again for a fresh result_url. Results stay available for 90 days.

Every error has the same shape:

{"error": {"type": "insufficient_credits", "message": "insufficient chips: available 3, needed 8"}}

• 400 · invalid_request_error
  The image can't be decoded, or its size is over the limits.
• 401 · authentication_error
  The key is missing, wrong or revoked.
• 402 · insufficient_credits
  Not enough chips for this photo — the message says how many are needed.
• 404 · invalid_request_error
  No such job (or not yours).
• 413 · invalid_request_error
  The file is larger than the upload limit.
• 415 · invalid_request_error
  Unsupported image format.
• 422 · invalid_request_error
  Bad upscale value, missing file, or an Idempotency-Key reused for a different photo.
• 429 · rate_limit_error
  Too many requests, or too many photos in progress at once. Honor Retry-After.
• 429 · spend_limit_reached
  Today's API spending limit is reached. Resets at 00:00 UTC.
• 500 · server_error
  Our fault. Retry — with the same Idempotency-Key for uploads.

• Up to 10 photos in progress at once per account. Past that, a new upload gets 429 and nothing is charged.
• Up to 100 uploads per minute per key; status requests are more generous.
• A daily spending limit through the API (UTC day), so a leaked key can't drain your balance — by default 5 000 chips a day. You can set a lower limit on your account page.

The API costs exactly what the site costs for the same photo and factor, paid from the same chip balance. The price grows with the size of the result: a 1 MP photo at ×4 costs about 3 chips, a 12 MP phone photo at ×2 about 7 chips. Chips cost $0.033–0.05 each depending on the pack. Check any size with /v1/quote; a failed job is refunded automatically. Buy chips on the pricing page; they never expire.

• Always send an Idempotency-Key (up to 128 characters, unique per photo) with uploads. Repeating the request with the same key returns the same job and charges once — so a timeout is always safe to retry.
• On 429 wait for Retry-After. On 5xx or a network error, retry with a growing pause (1 s, 2 s, 4 s…). Other 4xx errors won't succeed on retry — fix the request.
• Poll with ?wait=55 instead of calling every second.

The API is in public beta: there is no uptime guarantee yet, and we'll tell you by email about planned changes. Within /v1 we only add things — new fields, new error types — so ignore fields you don't know. Anything that would break an integration will ship as /v2, announced at least 90 days ahead.

Results belong to you. Use the API only for images you have the right to process. It must not be used for illegal content, sexual content involving minors, or intimate images of anyone without their consent. Accounts that break these rules or the Terms are blocked. Report abuse to [email protected]; questions go to [email protected].

Get your API key