Placid API

Name: Placid API API
Brand: Placid API
Availability: InStock

✓ Official Vendor SpecMediaVideo Processingbearer15 EndpointsREST

For Agents

Programmatically create a new image, retrieve an image by id. Covers 15 operations with bearer authentication.

Use for: I need to a new image, I want to an image by id, Search for an image by id, Find all a new video

Connect the Placid API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Placid 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.

Install Jentic One Beta (Self-Hosted)

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

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 Placid API API.

Create a new image

Retrieve an image by ID

Delete an image by ID

Use Cases

Patterns agents use Placid API API for, with concrete tasks.

GET STARTED

Start building with Placid API API

Explore with Jentic

View OpenAPI Document

Automated Images Management

Automate images operations by combining multiple Placid API endpoints. Agents can retrieve an image by id and then delete an image by id in a single workflow.

Call GET /images/{id} to retrieve an image by id, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Placid API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'create a new image', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

15 endpoints — api for generating images, videos, and pdfs from templates with dynamic content.

METHOD

PATH

DESCRIPTION

POST

/images

Create a new image

GET

/images/{id}

Retrieve an image by ID

DELETE

/images/{id}

Delete an image by ID

POST

/videos

Create a new video

GET

/videos/{id}

Retrieve a video by ID

DELETE

/videos/{id}

Delete a video by ID

POST

/pdfs

Create a new PDF

POST

/pdfs/merge

Merge multiple PDFs into one

POST

/images

Create a new image

GET

/images/{id}

Retrieve an image by ID

DELETE

/images/{id}

Delete an image by ID

POST

/videos

Create a new video

GET

/videos/{id}

Retrieve a video by ID

DELETE

/videos/{id}

Why though Jentic?

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

Credential isolation

Placid API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create a new image') and Jentic returns the matching Placid API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Placid API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Cloudinary

Alternative media API

Choose Cloudinary when you need a different approach to media operations

Alternative

Mux

Alternative media API

Choose Mux when you need a different approach to media operations

FAQs

Specific to using Placid API API through Jentic.

What authentication does the Placid API use?

The Placid API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I create a new image with the Placid API?

Yes. Use the POST /images endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Placid API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create a new image through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create a new image'. Jentic returns the matching Placid API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Placid API have?

The Placid API exposes 15 endpoints covering images, pdfs, templates operations.