Agent automation

Agent video workflow automation with Convertrilo MCP

Give MCP-capable agents a narrow video encoding tool surface for creating jobs, waiting for completion, inspecting reports, and handing outputs back to your workflow.

Convertrilo MCP is designed for agent hosts that need controlled media actions, not broad dashboard access. Agents can create, wait, cancel, and inspect jobs through scoped API keys.

Read MCP setupOpen npm packageDeveloper settings
Agent-safe MCP requestautomation
{
  "name": "create_encode_job",
  "arguments": {
    "sourceUrl": "https://example.com/input.mp4",
    "codec": "h264",
    "resolution": "1080p",
    "quality": "better",
    "audioPolicy": "transcode-aac",
    "frameRatePolicy": "cap",
    "scalePolicy": "no-upscale",
    "idempotencyKey": "asset-123:h264:1080p"
  }
}

Let agents create encoding jobs without full account access.

Require deterministic idempotency keys for retryable actions.

Inspect warnings and effectiveExecution before reporting success.

Cancel jobs explicitly when a workflow changes direction.

Workflow

Built for jobs that should run without a human babysitting a tab

Each automation page maps to the same production path: API request, durable job row, queue, Rust worker, storage upload, terminal event, and reconciliation.

  1. Step 1

    Install @convertrilo/sdk and run convertrilo login on the agent host.

  2. Step 2

    Register convertrilo-mcp as a local stdio MCP server.

  3. Step 3

    Ask the agent to create a job with explicit settings and an idempotency key.

  4. Step 4

    Have the agent wait for terminal status and inspect warnings before using the output.

Scoped tools

The MCP server exposes create, status, wait, cancel, and balance tools instead of arbitrary account operations.

Workflow-safe status

Terminal job status includes worker report fields that agents can summarize or branch on.

Environment override

Use CONVERTRILO_API_KEY for hosted agents or saved CLI config for local agent clients.

Automation questions

Should agents receive admin API keys?

No. Give agents scoped keys for the narrow workflow they are allowed to run.

Can an agent retry a failed create request?

Yes, if it uses the same idempotency key for the same intended job.

What should an agent inspect after completion?

At minimum, inspect status, downloadUrl or destination, warnings, sourceProbe, outputProbe, and effectiveExecution.

Related automation pages

API integration guideSDK, idempotency, S3, Google Drive, and webhook workflows.Video encoding APICreate video encoding jobs from your backend with API keys, idempotency, metadata, priority queues, webhooks, and storage destinations you control.Video encoding CLIAutomate video compression from terminals, deployment jobs, content pipelines, and scheduled scripts with a Convertrilo CLI workflow.Video encoding MCPConnect Convertrilo to MCP clients so agents can create encoding jobs, check status, wait for completion, cancel work, and inspect token balance.Video encoding webhooksReceive signed job.completed, job.failed, and job.canceled events so your app can publish assets, update records, and notify customers automatically.Batch video encodingQueue many videos from folders, asset libraries, imports, and customer batches with metadata, idempotency, webhooks, and storage destinations.Automated S3 video compressionCompress videos from S3-compatible storage and write finished MP4 outputs back to your own bucket with API keys, idempotency, and worker execution reports.Folder ingest automationQueue one encode job per video discovered in S3-compatible or Google Drive folders, with caps, metadata, output destinations, and webhook reconciliation.

Start with a real estimate

Choose your codec, resolution, FPS, bitrate, quality, and optimization settings. Convertrilo shows the NEU estimate before credits are reserved, and failed jobs release reserved credits back to your balance.

Start FreeCalculate Pricing