canonical: https://jentic.com/apis/filetypeconverters.com/filetypeconverters

# FileType Converters API

The FileType Converters API converts files between formats and tracks each conversion as a job. You can check which conversion pairs and formats are supported, submit a file to convert, poll the resulting job until it finishes, and download the output. Batch conversions run several files together and return their results as a ZIP, and a usage endpoint reports the entitlements left on your plan. Format and pair lookups are open, while converting and downloading require a credential.

## For AI agents

Convert files between formats as tracked jobs, check supported conversion pairs, poll job status, and download outputs. Run batch conversions and read plan usage and entitlements.

## Scope

Does not handle file hosting, long-term storage, or content editing. Use for converting files between formats and downloading the results only.

## Capabilities

- Convert a file from one format to another and track it as a job
- Check which conversion pairs and formats are supported before converting
- Poll a conversion job's status and download its output when it finishes
- Create a batch conversion and download the results as a ZIP
- Read your usage and entitlements to stay within plan limits

## Use cases

### Agent file conversion through Jentic

An AI agent that receives a file in the wrong format checks the supported pairs, submits the conversion, polls the job until it reports done, and downloads the result. Because the pair and format lookups are open, the agent can confirm a conversion is possible before spending a credential on it.

Example prompt: Check that a PDF to DOCX pair is supported, submit the conversion, poll the job until done, and download the output

### Batch conversion pipelines

Teams converting many files at once want a single handle to track them. The batch endpoint accepts a set of files, runs them together, and returns a ZIP of the outputs, so an integration can convert a folder of images or documents and fetch the archive in one step rather than managing each job by hand.

Example prompt: Create a batch conversion for several files, poll the batch status, and download the ZIP of results

### Capability discovery before conversion

Not every format pair is supported, and an agent should not guess. The open pairs and formats endpoints list exactly what can convert into what, so a workflow can validate a requested conversion up front and fall back gracefully when a pair is not available, before any credentialed call.

Example prompt: List supported formats and confirm whether a requested source-to-target pair is available

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v1/convert` | Convert a file |
| GET | `/api/v1/pairs` | Check conversion pairs |
| GET | `/api/v1/formats` | List formats and enabled pairs |
| GET | `/api/v1/jobs/{id}` | Get job status |
| GET | `/api/v1/jobs/{id}/download` | Download job output |
| POST | `/api/v1/batches` | Create a batch |
| GET | `/api/v1/batches/{id}` | Get batch status |
| GET | `/api/v1/usage` | Get usage and entitlements |

## Key resources

- **Conversions** — Submit a conversion and track it as a job, then download the output
- **Batches** — Run several conversions together and download the results as a ZIP
- **Formats** — List supported formats and conversion pairs
- **Usage** — Read plan usage and entitlements

## 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:** 42 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 65 / 100
  - AI-Readiness & Agent Experience: 18 / 100
  - Agent Usability: 94 / 100
  - Security: 55 / 100
  - AI Discoverability: 59 / 100
- **View full report:** https://jentic.com/apis/filetypeconverters.com/filetypeconverters/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 FileType Converters API by hand means choosing between a Bearer token and the X-API-Key header, polling each conversion job to completion, and tracking plan entitlements yourself. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** You choose which operations your agent may call, so it can convert files and download outputs while batch creation or usage reads stay out unless you add them. The format and pair lookups are open operations that need no credential.
- **Credential handling:** Your FileType Converters credential 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 'check supported conversion pairs', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **CloudConvert** — CloudConvert is a broad file conversion service, an alternative to FileType Converters across many formats.
- **ConvertAPI** — ConvertAPI converts documents and images between formats, an alternative conversion backend.
- **Filestack** — Filestack uploads and delivers files that can be fed into a FileType Converters conversion.

## FAQ

### What authentication does the FileType Converters API use?

It accepts a Bearer token or an X-API-Key header, per its OpenAPI spec. The format and pair lookups and the OpenAPI schema read need no credential, while converting, polling jobs, and downloading outputs require one.

### Can I check whether a conversion is supported with the FileType Converters API?

Yes. The pairs and formats endpoints are open and list exactly which source formats can convert into which targets, so you can validate a requested conversion before submitting it. That lets an agent fall back gracefully when a pair is not available instead of failing a credentialed call.

### What are the rate limits for the FileType Converters API?

The OpenAPI spec does not state a numeric rate limit, but it exposes a usage endpoint that reports the entitlements left on your plan. Read that endpoint and check the FileType Converters documentation to pace conversions within your plan.

### Is there a FileType Converters MCP server?

You don't need an MCP server to give your agent the FileType Converters API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the convert, job, batch, and usage operations on demand.

### Can I limit what my agent is allowed to do with the FileType Converters API?

Yes. Write a rule that allows the convert, job-status, and download operations and nothing else, so an agent can run conversions and fetch results while leaving batch creation or usage reads off unless you add them. The pair and format lookups are open operations that need no credential at all, and every call is recorded in your Jentic One audit log.

### How do I convert a file with the FileType Converters API through Jentic?

Search Jentic for 'convert a file to another format', add the FileType Converters API from the directory, and store your API key once; your agent then checks the pair, submits the conversion, polls the job, and downloads the output. To run it on your own infrastructure, install Jentic One from its GitHub repo.
