MegaPotato API is a REST API for photo super-resolution. Send an image and get it back 2×, 4× or 8× larger, up to 16 400 px on the long side, or sharper at its original size (1×). It runs the same models as the megapotato.app web app, tuned to keep the photo faithful while fur, hair, fabric and edges come back sharp.
Not a wrapper. We train our own super-resolution models and serve them from our own inference stack, engineered for speed and cost per photo: tiled GPU inference for very large outputs, scheduling that warms GPUs ahead of demand, calibrated per-job time estimates (eta_seconds) and a fast image pipeline for multi-megapixel files.
Two requests do the job
POST /v1/upscale: a multipart upload (PNG, JPG, WEBP or HEIC, up to 6 000 px and 40 MB) and the factor. Returns a job id and its price in chips.GET /v1/jobs/{id}?wait=55: long-polls until the job is done and returns a PNGresult_url.
Made for integrations: an Idempotency-Key on uploads so a retry never charges twice, one JSON error shape, Retry-After on 429, POST /v1/quote to price any size for free, a daily spending cap so a leaked key can't drain your balance, and results kept for 90 days.
Pricing: test keys (mp_test_…) run the whole flow for free and return a sample image. Live keys unlock with your first chip pack and use the same prepaid chips as the website: no subscription, packs from $5, chips never expire, and failed jobs are refunded automatically.
Examples for curl, Python and Node.js are in the GitHub repo (MIT). The API is in public beta: no SLA yet, and /v1 only changes in backward-compatible ways.
- Public beta API for AI image upscaling
- Use same model and chip prices as the MegaPotato site
- Two-step workflow: upload photo then retrieve result
- Test keys available for free trial without charges
- Transparent pricing and chip cost per upscale
MegaPotato API is a REST API that upscales photos up to 16 400 px using proprietary super-resolution models.
- for
- Developers who need programmatic image upscaling in apps or services.
- pricing
- paid · free trial
Key features
- Two-step workflow — Upload a photo with POST /v1/upscale, then get the result with one long-polling GET /v1/jobs/{id}?wait=55.
- Multiple upscale factors — Supports 1× (refine), 2×, 4× and 8× upscaling up to 16 400 px on the long side.
- Idempotent uploads — Idempotency-Key prevents double-charging on retries.
- Price quoting endpoint — POST /v1/quote returns chip cost for any size before processing.
- Daily spend cap — Default 5 000 chips per day limits accidental over-spending.
- Result retention — Results are kept for 90 days; each fetch returns a fresh download link valid for about an hour.
Use cases
- Generate high-resolution product photos for e-commerce catalogs
- Enhance user-uploaded images in a mobile app before display
- Create large-format prints from low-resolution source files
MegaPotato API pricing
- Starter$5.00one time100 chips · $0.05 per chip
- Plus$12.00one time250 chips · $0.048 per chip
- Creator$25.00one time600 chips · $0.0417 per chip
- Studio$50.00one time1 300 chips · $0.0385 per chip
- Agency$500.00one time15 000 chips · $0.0333 per chip
MegaPotato API vs alternatives
 MegaPotato API |  Percept Pixel |  removerized | |
|---|---|---|---|
| Best for | Fast, cost-predictable photo super-resolution | Global image CDN with transformations | Offline, open-source image upscaling |
| Pricing | Paid | Free | Free |
| DevHunt upvotes | 11 | 18 | 2 |
| Launched | Oct 2026 | Jan 2024 | Jun 2026 |
- MegaPotato API vs Percept Pixel: Offers CDN delivery and image transformations in addition to generation
- MegaPotato API vs removerized: Runs entirely locally/offline, whereas MegaPotato is a hosted API
MegaPotato API FAQ
How do I test the API without spending chips?+
Create a test key (mp_test_…) on your account page; the full flow runs but returns a sample image and costs nothing.
What image formats are supported?+
PNG, JPG, WEBP and HEIC up to 40 MB and 6 000 px on the long edge.
How are charges applied?+
The required number of chips is held from your balance when you upload and is deducted only after successful completion; failures are refunded.
What limits should I be aware of?+
Up to 10 concurrent jobs per account, 100 uploads per minute per key, and a daily spend limit (default 5 000 chips).
How do I handle rate-limit errors?+
Respect the Retry-After header on 429 responses and retry with exponential back-off for 5xx errors.
Is there an SLA or uptime guarantee?+
The API is in public beta with no SLA; breaking changes will be introduced only in a new major version (/v2).
Edited by the makers, based on megapotato.app · Sep 29, 2026. Details may change; check the official site.
