Apilayer Image Upload API
★ Only Publicly Available OpenAPI DocumentMediaImage ProcessingapiKey7 EndpointsREST
For Agents
Upload, transform, and serve images through 7 apilayer endpoints covering upload, resize, crop, optimize, and delete.
Use for: Upload a product photo to apilayer's image hosting, Pull an image from a remote URL and host it on apilayer, Resize an uploaded image to 800 by 600 pixels, Crop the top banner out of an uploaded image
Not supported: Does not handle video processing, AI background removal, or DAM-style metadata workflows — use for image upload, transformation, and retrieval only.
Jentic publishes the only available OpenAPI specification for the apilayer Image Upload API, keeping it validated and agent-ready. The Image Upload API uploads JPG, PNG, and GIF images directly or by URL, then exposes operations for resize, crop, and optimize. It is built for product catalogs and content sites that need a single vendor for storage and on-the-fly transformation, and authentication uses an apikey header issued from the apilayer dashboard. Seven endpoints cover the upload, retrieval, deletion, and three transformation actions.
Install Jentic One Beta
Connect the Image Upload API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Image Upload 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.
1
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 | sh2
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 instanceJentic 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 Image Upload API.
Upload an image directly via multipart POST or by URL with POST /upload/url
Retrieve image metadata and the hosted URL via GET /image/{imageId}
Resize an existing image to specified width and height via POST /resize
Crop an existing image to a target rectangle via POST /crop
Optimize an image's file size while preserving visible quality via POST /optimize
Delete a previously uploaded image via DELETE /image/{imageId} when it is no longer needed
Use Cases
Patterns agents use Image Upload API for, with concrete tasks.
★ Product image pipeline
Upload product photographs once via POST /upload, then call /resize, /crop, and /optimize to derive the thumbnails, hero images, and listing tiles a storefront needs. The Image Upload API hosts the resulting images so the storefront can serve them directly without operating its own CDN. This collapses what is usually a multi-tool pipeline into a small set of REST calls behind a single apikey.
POST /upload with the original image, then POST /resize with the returned imageId, width=800, and height=800 to produce a square thumbnail.
Content migration from external URLs
Move images already hosted elsewhere into apilayer's storage by passing the source URL to POST /upload/url. The API fetches and stores the image and returns a stable imageId you can use with /resize, /crop, and /optimize. This is well suited for migrating a blog or catalog onto apilayer without manually downloading and re-uploading every asset.
POST /upload/url with body {url:'https://oldsite.example.com/photo.jpg'} to import the image and receive its new imageId.
On-demand image optimization for performance
Run /optimize over uploaded images to reduce payload size for faster page loads, especially on mobile. The endpoint preserves visible quality while stripping unnecessary metadata and re-encoding more efficiently, and the optimized result can be retrieved through /image/{imageId}. This gives a cheap performance lift without changing the storefront's image markup.
POST /optimize with the imageId and optional quality parameter to produce a smaller file while keeping the same dimensions.
Agent-driven media operations
An AI agent maintaining a content catalog can call upload, transform, and delete operations through Jentic without ever holding the apilayer apikey. Jentic returns the relevant operation schemas on demand and injects credentials at execution time, so the agent's job is just to pick the right transformation for each piece of content.
Through Jentic, search 'upload and resize an image', load the apilayer.com /upload and /resize operations, and execute them in sequence with the new asset.
Key Endpoints
7 endpoints — jentic publishes the only available openapi specification for the apilayer image upload api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/upload
Upload an image via multipart
POST
/upload/url
Upload an image from a remote URL
POST
/resize
Resize an uploaded image
POST
/crop
Crop an uploaded image
POST
/optimize
Optimize file size of an uploaded image
GET
/image/{imageId}
Retrieve image metadata
DELETE
/image/{imageId}
Delete an uploaded image
POST
/upload
Upload an image via multipart
POST
/upload/url
Upload an image from a remote URL
POST
/resize
Resize an uploaded image
POST
/crop
Crop an uploaded image
POST
/optimize
Optimize file size of an uploaded image
GET
/image/{imageId}
Retrieve image metadata
DELETE
/image/{imageId}
Delete an uploaded image
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Your apilayer apikey is stored encrypted in the Jentic vault. Agents call operations through a scoped Jentic token and the apikey header is set at execution, so the raw key never reaches the agent.
Intent-based discovery
Agents search for intents like 'upload an image' or 'resize an image' and Jentic returns the apilayer.com Image Upload operations with their multipart and JSON input schemas.
Time to first call
Direct integration takes a few hours to wire up multipart uploads, error handling, and the transformation calls. Through Jentic the same flow is executable in under an hour.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Image Upload API through Jentic.
Why is there no official OpenAPI spec for the Image Upload API?
apilayer does not publish a standalone OpenAPI specification for the Image Upload API. Jentic generates and maintains this spec so that AI agents and developers can call Image Upload 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 Image Upload API use?
The API uses an apiKey passed in the apikey request header. Issue keys from the apilayer dashboard. Through Jentic, the apikey is held in the vault and added to the request server-side, so the raw key never reaches the agent.
Can I import an image from an existing URL instead of uploading bytes?
Yes. POST /upload/url with the source URL and apilayer fetches the image, stores it, and returns an imageId you can use with /resize, /crop, /optimize, or /image/{imageId}.
How do I run an image optimization through Jentic?
Search Jentic for 'optimize an image', load the apilayer.com /optimize operation, and execute with the imageId from a prior /upload call. The optimized image is retrievable via GET /image/{imageId}.
What formats does the Image Upload API support?
The spec describes JPG, PNG, and GIF inputs. /resize, /crop, and /optimize operate on those formats and return processed assets in the same family. WebP and HEIC are not declared in the spec.
What are the rate limits for the Image Upload API?
Rate limits are not declared in the OpenAPI spec. apilayer enforces monthly quotas tied to subscription plan, visible on the apilayer dashboard. Treat HTTP 429 as a signal to back off.
GET STARTED