For 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.
Use for: Convert a PDF to a Word document, Check whether a PNG to SVG conversion is supported, List the formats this service can convert, Get the status of a conversion job
Not supported: Does not handle file hosting, long-term storage, or content editing. Use for converting files between formats and downloading the results only.
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.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FileType Converters 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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffiletypeconverters.com%2Ffiletypeconverters" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffiletypeconverters.com%2Ffiletypeconverters" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with FileType Converters API.
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
Patterns agents use FileType Converters API for, with concrete tasks.
★ 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.
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.
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.
List supported formats and confirm whether a requested source-to-target pair is available
10 endpoints — the filetype converters api converts files between formats and tracks each conversion as a job.
METHOD
PATH
DESCRIPTION
/api/v1/convert
Convert a file
/api/v1/pairs
Check conversion pairs
/api/v1/formats
List formats and enabled pairs
/api/v1/jobs/{id}
Get job status
/api/v1/jobs/{id}/download
Download job output
/api/v1/batches
Create a batch
/api/v1/batches/{id}
Get batch status
/api/v1/usage
Get usage and entitlements
/api/v1/convert
Convert a file
/api/v1/pairs
Check conversion pairs
/api/v1/formats
List formats and enabled pairs
/api/v1/jobs/{id}
Get job status
/api/v1/jobs/{id}/download
Download job output
/api/v1/batches
Create a batch
/api/v1/batches/{id}
Get batch status
/api/v1/usage
Get usage and entitlements
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using FileType Converters API through Jentic.
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.
GET STARTED