Claid.ai Image Editing API

Name: Claid.ai Image Editing API API
Brand: Claid.ai Image Editing API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage Processingbearer11 EndpointsREST

For Agents

Run AI image edits — upscale, remove background, smart crop, convert formats — synchronously, asynchronously, or in batch through Claid.ai. Useful for any agent that needs to produce ecommerce-ready or social-ready images on demand.

Quickstart

Get started with Claid.ai Image Editing API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"remove image background"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Claid.ai Image Editing API API.

Apply AI image edits such as upscaling, background removal, and smart cropping in a single synchronous call

Submit large or slow edit jobs asynchronously and poll the job id for completion

Process many images in one batch and track the batch id through to completion

Upload an image directly to Claid for editing without first hosting it elsewhere

GET STARTED

Start building with Claid.ai Image Editing API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Claid.ai Image Editing API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Claid.ai Image Editing API, keeping it validated and agent-ready. Claid.ai applies AI-powered image edits — enhancement, upscaling, background removal, smart cropping, and format conversion — at scale through a single REST surface. The API offers synchronous, asynchronous, and batch processing modes, plus direct URL-based upload and persistent storage connectors so output can be written back to S3, GCS, or other targets without a round-trip through the caller. Authentication is by bearer token using a Claid.ai API key.

Use Cases

Patterns agents use Claid.ai Image Editing API API for, with concrete tasks.

★ Ecommerce product image pipeline

An online retailer feeds raw product photos through Claid to remove backgrounds, smart-crop to a consistent aspect ratio, and upscale for the product listing page. Large drops are submitted via POST /v1-beta1/image/edit/batch and the resulting batch id is polled with GET /v1-beta1/image/edit/batch/{batchId}. With a storage connector configured, the cleaned images land directly in the retailer's CDN bucket.

Submit a batch of 50 product image URLs to /v1-beta1/image/edit/batch with background removal and 1:1 smart crop, then poll the batch id every 30 seconds

On-demand social media image preparation

A social-publishing tool calls POST /v1-beta1/image/edit synchronously to crop and resize a hero image to multiple platform-specific dimensions in one request. The synchronous mode keeps the user-facing flow under a few seconds for typical input sizes, while async is reserved for heavier upscales. The bearer-token auth lets the publishing tool call Claid as a backend service without exposing the key to the browser.

POST /v1-beta1/image/edit with a source URL and a smart-crop preset for 1080x1350, then return the result URL

Storage connector setup for private buckets

Teams that do not want to relay images through their own infrastructure configure a storage connector via POST /v1-beta1/storage/connectors. Claid then writes edit outputs straight to the configured bucket and the team manages credentials in one place rather than per-request. GET, PUT, and DELETE on /v1-beta1/storage/connectors/{connectorId} cover the lifecycle.

Create an S3 storage connector for bucket 'product-images-prod' with the supplied access key, then verify it appears in GET /v1-beta1/storage/connectors

Agent integration via Jentic

Through Jentic, an agent helping a marketing team can resolve intents like 'upscale this image to 4K' to the right Claid endpoint and parameters without browsing the docs. The bearer API key is held in the Jentic credential vault and injected only at execution time.

Search Jentic for 'remove image background', load the schema for POST /v1-beta1/image/edit, and execute it with the user-supplied source URL

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for claid.

METHOD

PATH

DESCRIPTION

POST

/v1-beta1/image/edit

Edit an image synchronously

POST

/v1-beta1/image/edit/async

Submit an async edit job

GET

/v1-beta1/image/edit/async/{jobId}

Check async job status

POST

/v1-beta1/image/edit/batch

Submit a batch edit

GET

/v1-beta1/image/edit/batch/{batchId}

Check batch status

POST

/v1-beta1/image/edit/upload

Upload an image and edit it

POST

/v1-beta1/storage/connectors

Create a storage connector

GET

/v1-beta1/storage/connectors

List storage connectors

POST

/v1-beta1/image/edit

Edit an image synchronously

POST

/v1-beta1/image/edit/async

Submit an async edit job

GET

/v1-beta1/image/edit/async/{jobId}

Check async job status

POST

/v1-beta1/image/edit/batch

Submit a batch edit

GET

/v1-beta1/image/edit/batch/{batchId}

Check batch status

Why though Jentic?

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

Credential isolation

Claid.ai bearer keys are stored encrypted in the Jentic vault. The agent receives a scoped reference, not the raw key, so leaked transcripts cannot be replayed against Claid.

Intent-based discovery

Agents search Jentic with intents like 'upscale an image' or 'remove a background', and Jentic returns the matching Claid operation with its input schema and the right async or sync mode for the workload.

Time to first call

Direct integration with Claid: 1-2 days to read the docs, model sync vs async vs batch, and wire bearer auth. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Clarifai API

Clarifai classifies and labels images that Claid then edits or prepares for delivery.

Pair Clarifai (recognition) with Claid (editing) when the workflow needs both to understand and reformat an image.

Alternative

Clarifai

Clarifai's image inputs API overlaps for tagging and content-moderation, though it does not perform pixel-level edits.

Choose Clarifai when the need is content understanding rather than pixel transformation.

Complementary

Civic Auth API

Civic Auth gates the user identity that often sits in front of an image-upload pipeline.

Use Civic Auth to verify the uploader before passing image URLs into Claid for processing.

FAQs

Specific to using Claid.ai Image Editing API API through Jentic.

Why is there no official OpenAPI spec for Claid.ai Image Editing API?

Claid.ai does not publish an OpenAPI specification. Jentic generates and maintains this spec from the Claid developer documentation so AI agents and developers can call Claid through 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 Claid.ai API use?

Claid.ai uses HTTP bearer authentication — your Claid API key is sent as the bearer token in the Authorization header. Through Jentic, the key is stored encrypted in the credential vault and injected only at execution time.

Can I process many images in one call with Claid.ai?

Yes. POST /v1-beta1/image/edit/batch accepts a list of source images and a transformation set, and returns a batchId. Poll GET /v1-beta1/image/edit/batch/{batchId} for completion. For single heavy edits, the async endpoint at /v1-beta1/image/edit/async returns a jobId you poll the same way.

How do I remove a background through Jentic?

Search Jentic for 'remove image background'. Jentic returns POST /v1-beta1/image/edit with the input schema for transformations. Load the schema, set the background-removal flag in the operations payload, and execute it with the source image URL — no need to read the Claid docs first.

What are the rate limits for the Claid.ai API?

The OpenAPI spec does not declare formal rate limits. Claid applies per-account quotas tied to the plan; treat 429 responses as a signal to back off and confirm sustained throughput needs with Claid support before peak load.

Can Claid.ai write outputs directly to my own cloud storage?

Yes. Configure a storage connector via POST /v1-beta1/storage/connectors with credentials for an S3 or compatible bucket. Subsequent edit jobs can target that connector so Claid writes the result directly to your bucket without a round-trip through your servers.