What authentication does the Conversion Tools API use?

The API uses HTTP bearer authentication. Send your API token (from https://conversiontools.io/profile) in the Authorization: Bearer header on every call. Through Jentic the token sits in the vault and is injected at execution time so it never enters the agent's context.

How big a file can the Conversion Tools API handle?

The API supports streaming uploads up to 100GB via POST /files, after which a task is created with POST /tasks referencing the uploaded file_id. For very large files, prefer streaming uploads and webhook callbacks rather than synchronous polling.

Can I test conversions without using my paid quota?

Yes. Pass sandbox: true on the POST /tasks body and the conversion runs in sandbox mode without counting against your quota. This makes CI tests and integration validation free.

How do I run a file conversion through Jentic?

Run jentic search for 'convert a file', load the upload-and-task operations, then execute POST /files followed by POST /tasks with the source and target formats. Poll GET /tasks/{task_id} for status and GET /files/{file_id} to download the result.

What are the rate limits for the Conversion Tools API?

Rate limits are not declared in the OpenAPI spec. Conversion Tools applies plan-based quotas - see https://conversiontools.io for current tiers. Treat the upload and task endpoints as rate-limited per token and back off on HTTP 429 responses.

How do I delete files after a conversion is done?

Call POST /tasks/{task_id}/delete to remove the task's input and output files immediately, or use PATCH /tasks/{task_id}/retention to switch the task to a shorter retention mode. This is useful for sensitive documents that should not linger on the service.

Can I limit what my agent is allowed to do with the Conversion Tools API?

Yes. Because Jentic One is self-hosted, you set the rules for which Conversion Tools operations and credentials your agent may use. Since the targets are files and tasks the agent creates on the fly rather than fixed resources, you scope by operation: grant only the calls it needs, such as uploading a file with POST /files, creating a task with POST /tasks, and checking status with GET /tasks/{task_id}, while withholding calls like POST /tasks/{task_id}/delete. Every operation you credit the agent with stays inside that allowed set, so it cannot invoke anything you left out.