canonical: https://jentic.com/apis/rendi.dev/rendi-dev

# Rendi FFmpeg Command API

API for running FFmpeg in a cloud environment. The API exposes 10 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get command status, get list of commands sent. Covers 10 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get Command Status
- Run FFmpeg Command
- FFprobe and store a file
- Query and filter FFmpeg Command API records by parameters
- Monitor FFmpeg Command API operational status and events

## Use cases

### Developer Tools Operations

Use the FFmpeg Command API to perform developer tools operations programmatically. The API provides 10 endpoints covering core functionality including get command status, get list of commands sent, run ffmpeg command.

Example prompt: Call GET `/v1/commands/{command_id}` to get command status

### Automated API Management

Automate API operations by combining multiple FFmpeg Command API endpoints. Agents can get list of commands sent and then run ffmpeg command in a single workflow.

Example prompt: Call GET `/v1/commands` to get list of commands sent, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call FFmpeg Command 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 apiKey tokens manually.

Example prompt: Search Jentic for 'get command status', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/commands/{command_id}` | Get Command Status |
| GET | `/v1/commands` | Get list of commands sent |
| POST | `/v1/run-ffmpeg-command` | Run FFmpeg Command |
| POST | `/v1/run-chained-ffmpeg-commands` | Run Chained FFmpeg Commands which share input and output files |
| POST | `/v1/files/store-file` | FFprobe and store a file |
| GET | `/v1/files` | Get list of all stored files |
| GET | `/v1/files/{file_id}` | Get Stored File |
| DELETE | `/v1/files/{file_id}` | Delete Stored File in Rendi |

## Key resources

- **API** — Operations related to API
- **FFmpeg Commands** — Operations related to FFmpeg Commands
- **File Management** — Operations related to File Management

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 49 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 69 / 100
  - Developer Experience & Jentic Compatibility: 70 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 29 / 100
  - Security: 50 / 100
  - AI Discoverability: 71 / 100
- **View full report:** https://jentic.com/apis/rendi.dev/rendi-dev/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the FFmpeg Command API by hand means sending its X-API-KEY header to api.rendi.dev and mapping its command and file endpoints yourself. Through Jentic you install once, import the FFmpeg Command API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Rendi puts the command and file ids in the URL path (`/v1/commands/{command_id}`, `/v1/files/{file_id}`), so a rule can pin your agent to reading one command or file. You choose the operations it may call, so running commands or deleting files is not included unless you add them.
- **Credential handling:** Your Rendi API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get command status' or 'run an FFmpeg command', and Jentic returns the matching Rendi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the FFmpeg Command API use?

The FFmpeg Command API uses an API key passed in the `X-API-KEY` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get command status with the FFmpeg Command API?

Yes. Use the GET `/v1/commands/{command_id}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the FFmpeg Command 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 get command status through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get command status'. Jentic returns the matching FFmpeg Command API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the FFmpeg Command API have?

The FFmpeg Command API exposes 10 endpoints covering API, ffmpeg commands, file management operations.

### Can I limit what my agent is allowed to do with the FFmpeg Command API?

Yes. Jentic One is self-hosted by you, so your own rules decide which FFmpeg Command API operations and credentials the agent may use. You can allow read-only calls like GET `/v1/commands/{command_id}` to check command status or GET `/v1/files/{file_id}` to fetch a stored file, while withholding write operations such as POST `/v1/run-ffmpeg-command` or DELETE `/v1/files/{file_id}.` Because the command and file ids sit in the URL path, a rule can also pin the agent to a single command or file rather than the whole account.