Arize AX datasets, experiments, evaluators and tasks (BYOK)

Arize AX datasets, experiments, evaluators and tasks (BYOK) — connector documentation

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

What Arize AX datasets, experiments, evaluators and tasks (BYOK) is for

Arize AX datasets, experiments, evaluators and tasks (BYOK) lets an AI assistant read your own Arize AX Evals data through the Arize AX Evals API with a key you supply (Arize API key (user key or service key)). Read-only: 10 tools (list_datasets, get_dataset, list_experiments, get_experiment, list_experiment_runs, list_evaluators, get_evaluator, list_tasks, get_task, list_task_runs). 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.arize.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Arize AX Evals. Arize AX Evals 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 datasets exist in my Arize space?"
• "Show Arize dataset RGF0YXNldDox"
• "Which experiments ran against Arize dataset RGF0YXNldDox?"
• "Show Arize experiment RXhwOjE="
• "Which runs of Arize experiment RXhwOjE= errored?"
• "What evaluators do I have in Arize?"

What it does

• list_datasets: List Arize datasets with name, space and dates; example rows are not returned.
• get_dataset: Get one Arize dataset by id with its versions.
• list_experiments: List Arize experiments with the dataset they ran against and dates.
• get_experiment: Get one Arize experiment by id with dataset, version and trace project ids.
• list_experiment_runs: List the runs (one per dataset example) of an experiment with example id and error; model outputs and annotations are not picked.
• list_evaluators: List Arize evaluators (LLM and code judges) with type, description and dates; prompts and code are not returned.
• get_evaluator: Get one Arize evaluator by id with its type, description and dates.
• list_tasks: List Arize evaluation tasks (automated evaluations over a project or dataset) with sampling rate, continuous flag and last run time.
• get_task: Get one Arize evaluation task by id with sampling rate, evaluators and last run time.
• list_task_runs: List the runs of an Arize evaluation task with status, timing and success, error and skipped counts.

BYOK key

You bring your own Arize AX Evals Arize API key (user key or service key) (https://arize.com/docs/ax/security-and-settings/api-keys). 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.arize.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://arize.com/docs/ax/rest-reference/overview (the API this connector calls, with a BYOK key)

Live from the Arize AX Evals API (api.arize.com) with a BYOK key; documentation: https://arize.com/docs/ax/rest-reference/overview. 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 Arize AX Evals. Arize AX Evals 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 Arize AX Evals account.

Built for: Worldwide. Languages: English.

Arize AX datasets, experiments, evaluators and tasks (BYOK) — Privacy Policy

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

What Arize AX datasets, experiments, evaluators and tasks (BYOK) is. Arize AX datasets, experiments, evaluators and tasks (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Arize AX Evals data: Read your Arize AX datasets, experiments, evaluators, evaluation tasks and their runs with your own API key (global API host). You bring your own Arize AX Evals Arize API key (user key or service key); the assistant sends it to us with each request.

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

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

Children. Arize AX datasets, experiments, evaluators and tasks (BYOK) is a general-audience service operated by the adult using the assistant, under Arize AX Evals's own age rules.

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

Arize AX datasets, experiments, evaluators and tasks (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Arize AX datasets, experiments, evaluators and tasks (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Arize AX datasets, experiments, evaluators and tasks (BYOK) provides: Read your Arize AX datasets, experiments, evaluators, evaluation tasks and their runs with your own API key (global API host). 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 Arize AX Evals credentials and only access data you are allowed to access. Arize AX Evals's terms apply to your use of Arize AX Evals; 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 Arize AX Evals. Arize AX Evals 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 Arize AX Evals returns, lightly trimmed; it may be incomplete, delayed or changed by Arize AX Evals. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Arize AX Evals 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 Arize AX Evals'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; Arize AX Evals 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 Arize AX Evals 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 Arize AX Evals 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-arize-evals

Arize AX datasets, experiments, evaluators and tasks (BYOK) support

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

• MCP endpoint: https://byok-arize-evals.connectorbay.com/mcp
• REST API: https://byok-arize-evals.connectorbay.com/openapi.json
• Live status: https://byok-arize-evals.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. Arize AX datasets, experiments, evaluators and tasks (BYOK) never asks for them.