JIEZO Developer Portal

JIEZO is an open-source, browser-based screenshot editor with a small public HTTP API. This page is the entry point for building against it: the endpoints are unauthenticated, the contract is published as OpenAPI 3.1, and the whole application is Apache 2.0 on GitHub.

Start here

API documentation

Every public endpoint with request and response examples, plus the error-code table.

OpenAPI 3.1 specification

Machine-readable contract with operationIds, typed parameters, and response schemas.

Authentication and rate limits

No API key is required. Per-IP limits and 429 semantics.

llms.txt

Markdown site overview for AI agents and LLM crawlers.

llms-full.txt

Long-form Markdown reference covering features and the API.

Source code on GitHub

Apache 2.0. Issues, discussions, and self-hosting instructions.

API keys

There are none, and there is nothing to sign up for. The public API is anonymous and governed by per-IP rate limits instead of credentials. Details are in authentication and rate limits.

Quickstart

1. Capture a live page

No key, no signup. Post a URL and read back a base64 PNG.

curl -s -X POST https://kimte.com/api/screenshot \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com","deviceType":"desktop"}' \
  | jq -r .screenshot | base64 -d > shot.png

2. Optimize the export

Send the image back through Sharp to recompress it as WebP.

curl -s -X POST https://kimte.com/api/export \
  -F "image=@shot.png" \
  -F "format=webp" \
  -F "qualityPreset=high" \
  -o shot.webp

3. Handle failures

Every failing request returns the same JSON envelope. Branch on code.

{
  "error": "URL is required",
  "code": "invalid_request",
  "message": "URL is required",
  "hint": "Send a JSON body with a \"url\" string.",
  "status": 400,
  "documentation": "https://kimte.com/docs#errors"
}

Sandbox

There is no separate sandbox host. Production is safe to experiment against: the endpoints are read-only with respect to your data, nothing is stored against an account, and the editor itself never uploads your images. To run the full stack locally instead:

git clone https://kimte.com/contact.git
cd screenshot-studio
npm install
npm run dev

Building an agent

Load /openapi.json directly as a function-calling tool definition. Every operation carries a unique operationId, a description, typed parameters, and a response schema. Any page on this site also serves Markdown when asked:

curl -H "Accept: text/markdown" https://kimte.com/docs

CLI and MCP server

No official CLI tool and no MCP server are published yet. The curl examples above are the supported command-line path. If you want either one, open an issue.

Support

File bugs and feature requests on GitHub issues, or reach the maintainers through the contact page.