HTTP
POST /optimize converts and compresses a file or JSON image. Nothing is stored.
API and MCP, with an account
SEIRO has an HTTP API and an MCP server that convert and compress images in memory. They share the same capabilities. An account is required. There is no public key.
MCP
POST /mcp exposes optimize_image and list_capabilities. There is no login tool.
Account required
SEIRO people sign in with Desk. Everyone else requests access. Integration docs stay behind sign-in.
Capabilities
| Fact | HTTP | MCP |
|---|---|---|
| Convert and compress | POST /optimize | optimize_image |
| List limits | — | list_capabilities |
| Output | JPEG, PNG, WebP, AVIF, or auto | JPEG, PNG, WebP, AVIF, or auto |
| Input | HEIC, HEIF, JPEG, PNG, WebP, AVIF, GIF, TIFF, SVG | HEIC, HEIF, JPEG, PNG, WebP, AVIF, GIF, TIFF, SVG |
| Quality and size | Quality 1–100, fit, optional target bytes | Same |
| Edits | Crop, rotate, flip, flatten, sharpen, strip metadata | Same |
| Cap | 15 MB. inside fit does not enlarge. | Same |
| Storage | None | None |
| Auth | Account (Desk API key, MCP sign-in, or Desk session) | Same |
An account is required
The public site encodes in your browser and does not need an account. HTTP and MCP do. There is no self-serve key.
- SEIRO people: sign in with a Desk email and password. Integration docs appear below after sign-in.
- Everyone else: open Sign in, then I don't have an account. Tell us if you need HTTP, MCP, or batch encode.
Integration docs
Signed in. These files use your session. They are not public.
llms.txt
Loading…
AGENTS.md
Loading…
Questions
What is the image optimize API?
An HTTP endpoint and an MCP server that convert and compress images in memory. Output is JPEG, PNG, WebP, or AVIF. Nothing is stored. An account is required.
What can the HTTP API do?
POST /optimize accepts a file or JSON image. It converts to JPEG, PNG, WebP, or AVIF, with quality and optional max width and height. 15 MB cap. Input is HEIC, HEIF, JPEG, PNG, WebP, AVIF, GIF, TIFF, or SVG.
What can MCP do?
POST /mcp exposes optimize_image and list_capabilities. Same formats and limits as HTTP. There is no MCP login tool.
Do I need an account?
Yes. There is no public API key. SEIRO people sign in with a Desk account. Everyone else opens Sign in, then I don't have an account.
Does the API store images?
No. The file is processed in memory and returned. There is no bucket and no gallery.
Does the API accept HEIC?
Yes. Send HEIC or HEIF to POST /optimize or MCP optimize_image. Burst files use the first frame. Output is JPEG, PNG, WebP, or AVIF.