Install Jentic One Beta

Connect the Convert.Online API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Convert.Online 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%2Fconvert.online%2Fconvert-online" | sh

Step 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%2Fconvert.online%2Fconvert-online" | 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 Convert.Online API.

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

GET STARTED

Start building with Convert.Online API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Convert.Online API for, with concrete tasks.

★ 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.

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.

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.

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

9 endpoints — the convert.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Convert.Online API through Jentic.

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.

Convert.Online API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey, bearer9 EndpointsREST

For 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.

Use for: Convert a PNG image to WebP, Create a job that converts a document to PDF, List the formats a source file can be converted to, Upload a local file and start its conversion

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

14%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

64%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

47%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

67%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Convert.Online API to your agent

Capabilities

Start building with Convert.Online API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Convert.Online API

Jentic AI Readiness Score

Convert.Online API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness