Mux Data (BYOK)

Mux Data (BYOK) — connector documentation

• MCP endpoint: https://byok-mux-data.connectorbay.com/mcp
• REST API: POST https://byok-mux-data.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-mux-data.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Mux Data access token ID, sent in the X-Upstream-Key header and the access token secret in X-Upstream-Key-2 of every request (never stored, logged or cached)
• Health: https://byok-mux-data.connectorbay.com/health · Tool schemas: https://byok-mux-data.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-mux-data · agent@connectorbay.com

What Mux Data (BYOK) is for

Mux Data (BYOK) lets an AI assistant read your own Mux Data data through the Mux Data API with a key you supply (access token ID). Read-only: 11 tools (get_metric_overall, get_metric_timeseries, list_metric_breakdown, get_metric_insights, list_all_metric_values, list_dimensions, list_dimension_values, list_errors, list_incidents, list_annotations, get_realtime_breakdown). 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.mux.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Mux Data. Mux Data 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:

• "What was my median video startup time over the last 7 days in Mux?"
• "Show my Mux rebuffer percentage per day over the last 7 days"
• "Which countries have the worst video startup time in Mux this week?"
• "What is dragging down my Mux video startup time?"
• "Give me all my Mux Data metrics for the last day"
• "Which dimensions can I break Mux Data metrics down by?"

What it does

• get_metric_overall: Get the overall value of one Mux Data metric over a time window with total views, watch time and playing time. Aggregated, no viewer rows.
• get_metric_timeseries: Get one metric as a timeseries. Each data row is [timestamp, value, views]. Choose minute, ten_minutes, hour or day granularity.
• list_metric_breakdown: Break one metric down by a dimension (country, browser, video title, CDN and so on), with value, views, watch time and negative impact per row.
• get_metric_insights: List the dimension values that hurt a metric most: filter column, value, metric value, negative impact score and views.
• list_all_metric_values: List the values of all metrics at once for the whole property, or for one dimension value (for example country=US).
• list_dimensions: List the dimensions that Mux Data supports, split into basic and advanced ones.
• list_dimension_values: List the values seen for one dimension with the number of views for each value.
• list_errors: List playback errors seen in a time window: Mux error code, player error code, message, count, share of views and last seen time.
• list_incidents: List Mux Data incidents (alerts) with status, severity, impact, affected views, start and resolve time.
• list_annotations: List the notes (annotations) that were added to Mux Data charts, with date and note text.
• get_realtime_breakdown: Get live (last minutes) numbers for one real-time metric broken down by a dimension, with concurrent viewers per value.

BYOK key

You bring your own Mux Data access token ID (https://dashboard.mux.com/settings/access-tokens). 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.mux.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

• https://www.mux.com/docs/api-reference/data (the API this connector calls, with a BYOK key)

Live from the Mux Data API (api.mux.com) with a BYOK key; documentation: https://www.mux.com/docs/api-reference/data. 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 Mux Data. Mux Data 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 Mux Data account.

Built for: Worldwide. Languages: English.

Mux Data (BYOK) — Privacy Policy

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

What Mux Data (BYOK) is. Mux Data (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Mux Data data: Read your Mux Data video analytics with your own access token: QoE metrics, timeseries, breakdowns, errors, incidents and live concurrency. You bring your own Mux Data access token ID; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Mux Data 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.mux.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 Mux Data 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 Mux Data receives. The request we make on your behalf, including the key and the arguments, under Mux Data's own terms and privacy policy. Mux Data acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Mux Data 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 Mux Data 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. Mux Data (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 Mux Data at any time to end all access.

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

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

Mux Data (BYOK) — Terms of Service

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

1. The Service. Mux Data (BYOK) provides: Read your Mux Data video analytics with your own access token: QoE metrics, timeseries, breakdowns, errors, incidents and live concurrency. 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 Mux Data credentials and only access data you are allowed to access. Mux Data's terms apply to your use of Mux Data; 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 Mux Data. Mux Data 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 Mux Data returns, lightly trimmed; it may be incomplete, delayed or changed by Mux Data. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Mux Data 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 Mux Data'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; Mux Data 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 Mux Data 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 Mux Data 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-mux-data

Mux Data (BYOK) support

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

• MCP endpoint: https://byok-mux-data.connectorbay.com/mcp
• REST API: https://byok-mux-data.connectorbay.com/openapi.json
• Live status: https://byok-mux-data.connectorbay.com/health

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. Mux Data (BYOK) never asks for them.