canonical: https://jentic.com/apis/convert.online/convert-online

# Convert.Online API

The Convert.Online API converts files between more than 400 formats covering images, video, audio, documents, ebooks, archives, and fonts. A job is one conversion request whose tasks import a source, convert it, and export the result, so a single request can pull a file from storage, change its format, and hand back a download link. The API lists supported formats and per-conversion settings, accepts uploaded bytes through an import, and streams job progress as Server-Sent Events.

## For AI agents

Create file-conversion jobs across 400+ formats, upload source bytes, follow job progress, and download the result. Jobs authenticate with an API key or bearer token; the download link is tokened.

## Scope

Does not handle long-term file storage, document editing, or media streaming. Use for converting files between formats only.

## Capabilities

- List the supported formats and the settings a given conversion accepts
- Create a conversion job that imports a source, converts it, and exports the result
- Upload a local file's bytes to an import and start the conversion
- Follow a conversion job as it runs through Server-Sent Events
- Download a converted file through a tokened link
- Convert between images, video, audio, documents, ebooks, archives, and fonts

## Use cases

### Document and Image Conversion

An agent converts an uploaded document or image to a target format by creating a job, sending the source bytes to an import, and starting the conversion. Convert.Online supports more than 400 formats across documents, images, audio, and video, so one integration covers the formats an agent is likely to encounter without wiring a separate tool per file type.

Example prompt: Create a job with POST `/v1/process/jobs`, upload the source via PUT `/v1/imports/{importId}/content`, then call POST `/v1/process/jobs/{jobId}/complete-upload`

### Pipeline Conversion from Storage

A workflow agent wires a single job to import a file from a remote source, convert it, and export the result, then follows progress over Server-Sent Events until the download link is ready. Because a job's tasks are chained by their inputs, the agent orchestrates a multi-step conversion with one request rather than polling several endpoints.

Example prompt: Create the job with POST `/v1/process/jobs`, then stream GET `/v1/process/jobs/{jobId}/events` until the result is ready to download

### AI Agent Integration via Jentic

An AI agent reaches Convert.Online through Jentic without handling the API key itself. It searches by intent, receives the matching operation and its input schema, and executes the call with the credential injected at run time. This lets an agent convert a file mid-task without the builder wiring job creation and upload handling by hand.

Example prompt: Search Jentic for 'convert a file to another format', load the POST `/v1/process/jobs` schema, and execute it with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/formats` | List supported formats |
| POST | `/v1/process/jobs` | Create a conversion job |
| GET | `/v1/process/jobs/{jobId}` | Get a job |
| POST | `/v1/process/jobs/{jobId}/complete-upload` | Start the conversion once bytes have arrived |
| POST | `/v1/imports` | Create an import to receive a local file |
| GET | `/v1/download/{token}` | Download a converted file |

## Key resources

- **Formats** — List supported formats and per-conversion settings via `/v1/formats` and `/v1/options`
- **Jobs** — Create, read, and follow conversion jobs via `/v1/process/jobs`
- **Imports** — Create an import and send a local file's bytes via `/v1/imports`
- **Download** — Retrieve a converted file through a tokened link via `/v1/download/{token}`

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 51 / 100
  - Agent Usability: 94 / 100
  - Security: 55 / 100
  - AI Discoverability: 67 / 100
- **View full report:** https://jentic.com/apis/convert.online/convert-online/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 Convert.Online by hand means managing its API key, choosing between the bearer and X-API-Key headers, and orchestrating the import, convert, and download steps of a job yourself. Through Jentic you install once, import Convert.Online from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Convert.Online puts the job id in the URL path (`/v1/process/jobs/{jobId}`), so a rule can pin your agent to one job: it can create a conversion and read that job's status and nothing else. You choose which operations it may call, so job creation and the status read can be allowed while other operations stay out of reach.
- **Credential handling:** Your Convert.Online 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 'convert a file to another format' or 'list supported formats', and Jentic returns the matching Convert.Online operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **CloudConvert** — Established file-conversion API covering a broad range of formats
- **iLovePDF** — PDF-focused tooling for merge, split, compress, and convert
- **Filestack** — File upload, storage, and delivery with transformation URLs

## FAQ

### What authentication does the Convert.Online API use?

The Convert.Online API authenticates with an API key, sent either as a bearer token in the Authorization header or in the X-API-Key header, per its OpenAPI spec. The tokened download link needs no credential. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.

### What formats can the Convert.Online API convert between?

The API converts between more than 400 formats spanning images, video, audio, documents, ebooks, archives, and fonts. The formats operation lists what is supported and the options operation returns the settings a given conversion accepts, so an agent can confirm a target format is available before creating a job.

### What are the rate limits for the Convert.Online API?

The OpenAPI spec does not publish specific rate-limit numbers; check https://api.convert.online for the current limits on your plan. Conversion runs as an asynchronous job, so an agent follows progress over the job's event stream rather than polling tightly.

### Is there a Convert.Online MCP server?

You don't need an MCP server to give your agent Convert.Online. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the job and import operations. Nothing extra is loaded into the agent's context until an operation is actually invoked.

### Can I limit what my agent is allowed to do with the Convert.Online API?

Yes. Convert.Online puts the job id in the URL path, so write a rule that allows job creation and the read on `/v1/process/jobs/{jobId}`, and the agent can convert files and check their status without reaching anything else. Every call runs through your own Jentic One instance and is logged for you to review.

### How do I convert a file with the Convert.Online API through Jentic?

Search Jentic for 'convert a file to another format', and it returns the Convert.Online job operation with its input schema. Load the schema and execute POST `/v1/process/jobs` with the source and target format, with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
