CheetahO Image Optimization API

Name: CheetahO Image Optimization API
Brand: CheetahO Image Optimization API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage ProcessingapiKey2 EndpointsREST

For Agents

Compress, resize, and convert images to WebP through one optimisation endpoint, with an account endpoint for quota lookup.

Install Jentic One Beta

Connect the CheetahO Image Optimization API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CheetahO Image Optimization API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with CheetahO Image Optimization API.

Compress JPEG, PNG, and GIF images using lossy or lossless settings

Resize an image to a target width or height as part of the same optimisation call

Convert images to WebP for smaller payloads on supporting clients

GET STARTED

Start building with CheetahO Image Optimization API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for CheetahO Image Optimization API, keeping it validated and agent-ready. CheetahO compresses and resizes JPEG, PNG, and GIF images using lossy or lossless algorithms, with WebP conversion and custom quality controls. The API exposes a single optimisation endpoint that accepts a source image and returns an optimised version, plus an account endpoint for plan and quota information. It is designed for teams that need to shrink images at the point of upload, in a build pipeline, or before delivering them through a CDN.

Use Cases

Patterns agents use CheetahO Image Optimization API for, with concrete tasks.

★ Build-Pipeline Image Optimisation

Wire CheetahO into a static-site or front-end build so every image is compressed and optionally converted to WebP at deploy time. POST /api/v2/media/optimization accepts the source image plus optimisation parameters and returns the optimised result. The build step replaces a manual round of image squashing in a desktop tool and keeps page weight low without ongoing maintenance.

Optimise the file 'hero.png' with lossy=true and resize_width=1600, save the response, and report the size reduction in bytes.

User-Generated Content Compression

Compress photos uploaded by end users (marketplaces, community sites, classifieds) before they hit object storage. The API accepts each upload, returns a smaller file, and the application persists only the optimised copy. WebP conversion is offered for clients that support it, with fallbacks served in the original format. Reduces storage and bandwidth costs without writing custom image-magick pipelines.

Send a user-uploaded JPEG to /api/v2/media/optimization with quality=82 and return the optimised binary.

Quota Monitoring and Plan Sizing

GET /api/v2/user returns account data including plan and usage figures, so a team can monitor quota burn-down and decide whether to upgrade before hitting limits. A nightly cron calls the endpoint, writes results to a metrics store, and alerts when remaining quota falls below a threshold. Avoids surprise overages on busy launch days.

Call GET /api/v2/user once a day, store the remaining-credits figure, and trigger a Slack alert when it falls below 1000.

AI Agent Asset Pipelines

Through Jentic, an AI agent can be asked to 'shrink these product images and convert them to WebP' as part of a larger e-commerce or content workflow. The agent searches for 'optimize an image', loads the CheetahO schema, and executes per file without ever holding the raw API key. Pair with a storage or CDN API to fetch sources and write outputs in the same agent run.

Search Jentic for 'optimize an image', load the CheetahO schema, and run the call against three product photos with lossless=true.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for cheetaho image optimization api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/v2/media/optimization

Optimise an image

GET

/api/v2/user

Get user account and quota data

POST

/api/v2/media/optimization

Optimise an image

GET

/api/v2/user

Get user account and quota data

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

CheetahO API keys are stored encrypted in the Jentic vault. Agents receive scoped tokens and execute calls through Jentic — the raw 'key' header value never enters agent context.

Intent-based discovery

Agents search by intent (e.g., 'optimize an image' or 'get account usage') and Jentic returns the matching CheetahO operation with its input schema, so the agent calls the right endpoint without reading the docs.

Time to first call

Direct CheetahO integration: a few hours to wire upload and result handling. Through Jentic: under 15 minutes from search to first optimised image.

FAQs

Specific to using CheetahO Image Optimization API through Jentic.

Why is there no official OpenAPI spec for CheetahO Image Optimization API?

CheetahO does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CheetahO Image Optimization API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the CheetahO Image Optimization API use?

The API uses an API key passed in the 'key' header. Keys are issued from the API Credentials section of the CheetahO dashboard. Through Jentic, the key is stored encrypted in the credential vault and injected at execute time, so the agent never holds the raw value.

Can I convert an image to WebP with the CheetahO API?

Yes. POST /api/v2/media/optimization accepts WebP conversion as part of its optimisation parameters alongside compression and resizing options. A single call can resize, compress, and convert in one round trip.

What are the rate limits for the CheetahO Image Optimization API?

The OpenAPI spec does not declare numeric rate limits. CheetahO enforces per-plan monthly quotas; GET /api/v2/user returns the current usage and plan so callers can monitor burn-down rather than rely solely on 429 handling.

How do I optimise an image and check my quota through Jentic?

Search Jentic for 'optimize an image', load the schema for POST /api/v2/media/optimization, and execute with the source file and parameters. Then search 'get user account', load GET /api/v2/user, and execute to confirm remaining credits — two operations from intent to actionable result.

Which image formats are supported?

The API supports JPEG, PNG, and GIF inputs and can output the same formats or convert to WebP. Lossy and lossless modes are available, and a custom quality value lets callers tune the size-versus-fidelity trade-off per image.