Thousand Eyes (BYOK)

Thousand Eyes (BYOK) — connector documentation

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

What Thousand Eyes (BYOK) is for

Thousand Eyes (BYOK) lets an AI assistant read your own Thousand Eyes data through the Thousand Eyes API with a key you supply (ThousandEyes user API token (OAuth bearer token)). Read-only: 9 tools (list_account_groups, get_account_group, get_current_user, list_tests, list_agents, list_alerts, get_alert, list_alert_rules, list_alert_suppression_windows). 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.thousandeyes.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Thousand Eyes. Thousand Eyes 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 ThousandEyes account groups can I access?"
• "Show details of ThousandEyes account group 1234"
• "Which ThousandEyes user is this token for?"
• "Which ThousandEyes tests are configured and how often do they run?"
• "Which ThousandEyes enterprise agents are offline?"
• "Which ThousandEyes alerts fired in the last 24 hours?"

What it does

• list_account_groups: List the account groups the token's user belongs to, with their ids (aid). Use an id as the aid parameter of other tools.
• get_account_group: Get one account group: name, whether it is the current or default one, and its organization name and id. Users and tokens are not returned.
• get_current_user: Show the user the token belongs to: name, user id, registration date, last login and login account group.
• list_tests: List the tests configured in an account group with type, interval, enabled flags and creation and modification dates.
• list_agents: List the Cloud and Enterprise Agents visible to the account group, with location, network, state and (for Enterprise Agents) hostname and last-seen time.
• list_alerts: List alerts (active ones by default, or cleared ones with state=clear) in a lookback window or date range, with type, severity, start and end time and violation count.
• get_alert: Get one alert by id with its type, state, severity, times and violation count.
• list_alert_rules: List the alert rules with expression, alert type, direction, minimum sources, rounds-violating settings and severity.
• list_alert_suppression_windows: List alert suppression (maintenance) windows with name, status, start, duration and repeat settings.

BYOK key

You bring your own Thousand Eyes ThousandEyes user API token (OAuth bearer token) (https://developer.cisco.com/docs/thousandeyes/authentication/). 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.thousandeyes.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://developer.cisco.com/docs/thousandeyes/ (the API this connector calls, with a BYOK key)

Live from the Thousand Eyes API (api.thousandeyes.com) with a BYOK key; documentation: https://developer.cisco.com/docs/thousandeyes/. 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 Thousand Eyes. Thousand Eyes 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 Thousand Eyes account.

Built for: Worldwide. Languages: English.

Thousand Eyes (BYOK) — Privacy Policy

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

What Thousand Eyes (BYOK) is. Thousand Eyes (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Thousand Eyes data: Read your ThousandEyes network monitoring tests, agents, alerts, alert rules, suppression windows and account groups with your own API token. You bring your own Thousand Eyes ThousandEyes user API token (OAuth bearer token); the assistant sends it to us with each request.

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

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

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

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

Thousand Eyes (BYOK) — Terms of Service

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

1. The Service. Thousand Eyes (BYOK) provides: Read your ThousandEyes network monitoring tests, agents, alerts, alert rules, suppression windows and account groups with your own API token. 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 Thousand Eyes credentials and only access data you are allowed to access. Thousand Eyes's terms apply to your use of Thousand Eyes; 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 Thousand Eyes. Thousand Eyes 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 Thousand Eyes returns, lightly trimmed; it may be incomplete, delayed or changed by Thousand Eyes. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Thousand Eyes 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 Thousand Eyes'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; Thousand Eyes 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 Thousand Eyes 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 Thousand Eyes 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-thousandeyes

Thousand Eyes (BYOK) support

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

• MCP endpoint: https://byok-thousandeyes.connectorbay.com/mcp
• REST API: https://byok-thousandeyes.connectorbay.com/openapi.json
• Live status: https://byok-thousandeyes.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. Thousand Eyes (BYOK) never asks for them.