Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Bitmovin Encoding (BYOK) icon

Bitmovin Encoding (BYOK)

Read your Bitmovin video encodings, their status, streams, muxings, inputs, outputs and HLS or DASH manifests with your own API key

Unify Dynamics LLC

Tools10read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderBitmovin Encodingunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which Bitmovin encodings are running right now?
Tools called
list_encodings
Show the details of Bitmovin encoding d8b5a1c0-3f4e-4a1b-9c2d-0e6f7a8b9c10
Tools called
get_encoding
How far along is Bitmovin encoding d8b5a1c0-3f4e-4a1b-9c2d-0e6f7a8b9c10?
Tools called
get_encoding_status
What streams does Bitmovin encoding d8b5a1c0-3f4e-4a1b-9c2d-0e6f7a8b9c10 have?
Tools called
list_encoding_streams
Which muxings were produced by Bitmovin encoding d8b5a1c0-3f4e-4a1b-9c2d-0e6f7a8b9c10?
Tools called
list_encoding_muxings
Which input sources are set up in my Bitmovin account?
Tools called
list_inputs

About

Bitmovin Encoding (BYOK) lets an AI assistant read your own Bitmovin Encoding data through the Bitmovin Encoding API with a key you supply (Bitmovin API key). Read-only: 10 tools (list_encodings, get_encoding, get_encoding_status, list_encoding_streams, list_encoding_muxings, list_inputs, list_outputs, list_manifests, list_hls_manifests, list_dash_manifests). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.bitmovin.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Bitmovin Encoding. Bitmovin Encoding and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Bitmovin Encoding API (api.bitmovin.com) with a BYOK key; documentation: https://developer.bitmovin.com/encoding/reference/. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

10 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data10 tools
  • List encodingsList video encodings with their details, filtered by status, type, name or creation time.
  • Get encodingGet one encoding: name, progress, encoder version, queued, started and finished times, labels.
  • Get encoding statusGet the live progress of an encoding: percent done, estimated time left, sub-task states, messages and any error.
  • List encoding streamsList the streams of an encoding (each maps an input to a codec configuration).
  • List encoding muxingsList all muxings (output containers such as fMP4, TS or MP4) of an encoding.
  • List inputsList the configured inputs (storage locations and live ingest points that encodings read from), optionally by name or type.
  • List outputsList the configured outputs (storage locations encodings write to), optionally by name or type.
  • List manifestsList all manifests (HLS, DASH and Smooth Streaming) with their type, name and status.
  • List hls manifestsList HLS manifests, optionally only those that belong to one encoding.
  • List dash manifestsList DASH manifests, optionally only those that belong to one encoding.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-bitmovin.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 10 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-bitmovin.connectorbay.com/mcp
RESTPOST https://byok-bitmovin.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-bitmovin.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Bitmovin API key in the X-Upstream-Key header (get one at dashboard.bitmovin.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Bitmovin Encoding connector: questions and answers

What is the Bitmovin Encoding connector?

Bitmovin Encoding (BYOK) lets an AI assistant read your own Bitmovin Encoding data through the Bitmovin Encoding API with a key you supply… It is a hosted MCP server with 10 tools such as List encodings, Get encoding, Get encoding status, List encoding streams, List encoding muxings, List inputs, published by Unify Dynamics LLC. It is independent and not affiliated with Bitmovin Encoding.

How do I connect Bitmovin Encoding to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-bitmovin.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-bitmovin.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-bitmovin.json.

Do I need a Bitmovin Encoding account or API key?

Yes: this is a bring-your-own-key connector. Create a Bitmovin API key at https://dashboard.bitmovin.com/account and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Bitmovin Encoding read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Bitmovin Encoding connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Fleet Device Management (BYOK)

Read your Fleet (osquery device management) hosts, labels, policies, software, operating systems and vulnerabilities with your own API token; no lock, wipe or other device actions

Live · MCP + REST10 tools

Flightcontrol (BYOK)

Read your Flightcontrol projects, services, scaling, deployments, custom domains and AWS account links with your own organization API key

Live · MCP + REST11 tools

Flotiq (BYOK)

Read the content types, content objects, media library and full-text search of your Flotiq headless CMS with your own read-only API key

Live · MCP + REST6 tools

Flowise Cloud (BYOK)

Read your Flowise Cloud chatflows, agent flows, assistants, custom tools and document stores with your own Flowise API key (no prompts or flow definitions)

Live · MCP + REST8 tools

Flowroute (BYOK)

Read your Flowroute phone numbers, inbound routes, caller ID name records, message records and statistics, and port order status with your own access key and secret

Live · MCP + REST9 tools

Fly.io Machines (BYOK)

Read your Fly.io apps, Machines, volumes, certificates, IP addresses and regions through the Machines API with BYOK

Live · MCP + REST9 tools

Documentation

Back to top

Bitmovin Encoding (BYOK) — connector documentation

  • MCP endpoint: https://byok-bitmovin.connectorbay.com/mcp
  • REST API: POST https://byok-bitmovin.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-bitmovin.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Bitmovin Encoding Bitmovin API key, sent in the X-Upstream-Key header and the organization id (X-Tenant-Org-Id, only needed for multi-organization accounts; otherwise enter any value from your account) in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-bitmovin.connectorbay.com/health · Tool schemas: https://byok-bitmovin.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-bitmovin · agent@connectorbay.com

What Bitmovin Encoding (BYOK) is for

Bitmovin Encoding (BYOK) lets an AI assistant read your own Bitmovin Encoding data through the Bitmovin Encoding API with a key you supply (Bitmovin API key). Read-only: 10 tools (list_encodings, get_encoding, get_encoding_status, list_encoding_streams, list_encoding_muxings, list_inputs, list_outputs, list_manifests, list_hls_manifests, list_dash_manifests). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.bitmovin.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Bitmovin Encoding. Bitmovin Encoding and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Bitmovin encodings are running right now?"
  • "Show the details of Bitmovin encoding d8b5a1c0-3f4e-4a1b-9c2d-0e6f7a8b9c10"
  • "How far along is Bitmovin encoding d8b5a1c0-3f4e-4a1b-9c2d-0e6f7a8b9c10?"
  • "What streams does Bitmovin encoding d8b5a1c0-3f4e-4a1b-9c2d-0e6f7a8b9c10 have?"
  • "Which muxings were produced by Bitmovin encoding d8b5a1c0-3f4e-4a1b-9c2d-0e6f7a8b9c10?"
  • "Which input sources are set up in my Bitmovin account?"

What it does

  • list_encodings: List video encodings with their details, filtered by status, type, name or creation time. Bitmovin keeps encoding history for 90 days.
  • get_encoding: Get one encoding: name, progress, encoder version, queued, started and finished times, labels.
  • get_encoding_status: Get the live progress of an encoding: percent done, estimated time left, sub-task states, messages and any error.
  • list_encoding_streams: List the streams of an encoding (each maps an input to a codec configuration).
  • list_encoding_muxings: List all muxings (output containers such as fMP4, TS or MP4) of an encoding.
  • list_inputs: List the configured inputs (storage locations and live ingest points that encodings read from), optionally by name or type.
  • list_outputs: List the configured outputs (storage locations encodings write to), optionally by name or type.
  • list_manifests: List all manifests (HLS, DASH and Smooth Streaming) with their type, name and status.
  • list_hls_manifests: List HLS manifests, optionally only those that belong to one encoding.
  • list_dash_manifests: List DASH manifests, optionally only those that belong to one encoding.

BYOK key

You bring your own Bitmovin Encoding Bitmovin API key (https://dashboard.bitmovin.com/account). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.bitmovin.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Bitmovin Encoding API (api.bitmovin.com) with a BYOK key; documentation: https://developer.bitmovin.com/encoding/reference/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Bitmovin Encoding. Bitmovin Encoding and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Bitmovin Encoding account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Bitmovin Encoding (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Bitmovin Encoding (BYOK) is. Bitmovin Encoding (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Bitmovin Encoding data: Read your Bitmovin video encodings, their status, streams, muxings, inputs, outputs and HLS or DASH manifests with your own API key. You bring your own Bitmovin Encoding Bitmovin API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Bitmovin Encoding call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.bitmovin.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Bitmovin Encoding rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Bitmovin Encoding receives. The request we make on your behalf, including the key and the arguments, under Bitmovin Encoding's own terms and privacy policy. Bitmovin Encoding acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Bitmovin Encoding gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Bitmovin Encoding data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Bitmovin Encoding (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Bitmovin Encoding at any time to end all access.

Children. Bitmovin Encoding (BYOK) is a general-audience service operated by the adult using the assistant, under Bitmovin Encoding's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Bitmovin Encoding (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Bitmovin Encoding (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Bitmovin Encoding (BYOK) provides: Read your Bitmovin video encodings, their status, streams, muxings, inputs, outputs and HLS or DASH manifests with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Bitmovin Encoding credentials and only access data you are allowed to access. Bitmovin Encoding's terms apply to your use of Bitmovin Encoding; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Bitmovin Encoding. Bitmovin Encoding and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Bitmovin Encoding returns, lightly trimmed; it may be incomplete, delayed or changed by Bitmovin Encoding. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Bitmovin Encoding account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Bitmovin Encoding's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Bitmovin Encoding may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Bitmovin Encoding key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Bitmovin Encoding takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-bitmovin

Bitmovin Encoding (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Bitmovin Encoding (BYOK) never asks for them.

Get Bitmovin Encoding (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Bitmovin Encoding Bitmovin API key. Create one at https://dashboard.bitmovin.com/account, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Bitmovin Encoding. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Bitmovin Encoding.