Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Arize AX organizations, spaces, projects and monitors (BYOK) icon

Arize AX organizations, spaces, projects and monitors (BYOK)

Read your Arize AX organizations, spaces, projects, monitors and AI integration names with your own API key (global API host)

Unify Dynamics LLC

Tools9read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderArize AX Workspaceunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

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

Which Arize organizations can my key access?
Tools called
list_organizations
Show Arize organization T3JnOjE=
Tools called
get_organization
What Arize spaces do I have?
Tools called
list_spaces
Show Arize space U3BhY2U6MQ==
Tools called
get_space
Which projects are in my Arize space?
Tools called
list_projects
Show Arize project UHJvamVjdDox
Tools called
get_project

About

Arize AX organizations, spaces, projects and monitors (BYOK) lets an AI assistant read your own Arize AX Workspace data through the Arize AX Workspace API with a key you supply (Arize API key (user key or service key)). Read-only: 9 tools (list_organizations, get_organization, list_spaces, get_space, list_projects, get_project, list_monitors, get_monitor, list_ai_integrations). 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 Workspace. Arize AX Workspace and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Arize AX Workspace 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.

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

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

OpenAPI
Read your data9 tools
  • List organizationsList the Arize organizations the key can see with name, description and creation time.
  • Get organizationGet one Arize organization by id.
  • List spacesList Arize spaces (workspaces that hold projects, datasets and prompts) with name, privacy flag and organization.
  • Get spaceGet one Arize space by id with its organization, privacy flag and creation time.
  • List projectsList Arize projects (LLM applications and model projects that collect traces) with space, type and creation time.
  • Get projectGet one Arize project by id with its space, type and creation time.
  • List monitorsList Arize monitors with type, status (TRIGGERED, CLEARED or NO_DATA), latest computed value and last evaluation time.
  • Get monitorGet one Arize monitor by id with type, status, latest computed value and dates.
  • List ai integrationsList the AI provider integrations configured for evaluators: provider, base URL and model names (keys and headers are not returned).

Information

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

Connect it to your agent

Three ways in, the same 9 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-arize-workspace.connectorbay.com/mcp
RESTPOST https://byok-arize-workspace.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-arize-workspace.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 Arize API key (user key or service key) in the X-Upstream-Key header (get one at arize.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Arize AX organizations, spaces, projects and monitors connector: questions and answers

What is the Arize AX organizations, spaces, projects and monitors connector?

Arize AX organizations, spaces, projects and monitors (BYOK) lets an AI assistant read your own Arize AX Workspace data through the Arize AX… It is a hosted MCP server with 9 tools such as List organizations, Get organization, List spaces, Get space, List projects, Get project, published by Unify Dynamics LLC. It is independent and not affiliated with Arize AX Workspace.

How do I connect Arize AX organizations, spaces, projects and monitors to Claude, ChatGPT or Cursor?

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

Do I need a Arize AX Workspace account or API key?

Yes: this is a bring-your-own-key connector. Create a Arize API key (user key or service key) at https://arize.com/docs/ax/security-and-settings/api-keys 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 Arize AX organizations, spaces, projects and monitors read-only?

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

Is the Arize AX organizations, spaces, projects and monitors 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

Paris Open Data (BYOK)

Browse and query the open datasets of the City of Paris open data portal (Opendatasoft Explore API) with your own portal API key

Live · MCP + REST7 tools

Particle (BYOK)

Read your Particle IoT devices, their online status and firmware, and product fleets with BYOK

Live · MCP + REST4 tools

Particle (BYOK)

Read your Particle IoT devices and cloud variables, call a device function and flash a device LED to find it, with your own access token

Live · MCP + REST4 tools

Particle Libraries (BYOK)

Browse the Particle firmware library catalog and the firmware build targets (Device OS versions per platform) with your own access token

Live · MCP + REST5 tools

Particle (BYOK)

Read the devices, device groups and cloud variables of your Particle product fleet and call a function on one product device, with your own access token

Live · MCP + REST4 tools

Particle Products (BYOK)

Read your Particle IoT products, product firmware versions, device groups, fleet traffic metrics and fleet SIM data usage with your own access token

Live · MCP + REST10 tools

Documentation

Back to top

Arize AX organizations, spaces, projects and monitors (BYOK) — connector documentation

  • MCP endpoint: https://byok-arize-workspace.connectorbay.com/mcp
  • REST API: POST https://byok-arize-workspace.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-arize-workspace.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Arize AX Workspace 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-workspace.connectorbay.com/health · Tool schemas: https://byok-arize-workspace.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-arize-workspace · agent@connectorbay.com

What Arize AX organizations, spaces, projects and monitors (BYOK) is for

Arize AX organizations, spaces, projects and monitors (BYOK) lets an AI assistant read your own Arize AX Workspace data through the Arize AX Workspace API with a key you supply (Arize API key (user key or service key)). Read-only: 9 tools (list_organizations, get_organization, list_spaces, get_space, list_projects, get_project, list_monitors, get_monitor, list_ai_integrations). 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 Workspace. Arize AX Workspace 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 Arize organizations can my key access?"
  • "Show Arize organization T3JnOjE="
  • "What Arize spaces do I have?"
  • "Show Arize space U3BhY2U6MQ=="
  • "Which projects are in my Arize space?"
  • "Show Arize project UHJvamVjdDox"

What it does

  • list_organizations: List the Arize organizations the key can see with name, description and creation time.
  • get_organization: Get one Arize organization by id.
  • list_spaces: List Arize spaces (workspaces that hold projects, datasets and prompts) with name, privacy flag and organization.
  • get_space: Get one Arize space by id with its organization, privacy flag and creation time.
  • list_projects: List Arize projects (LLM applications and model projects that collect traces) with space, type and creation time.
  • get_project: Get one Arize project by id with its space, type and creation time.
  • list_monitors: List Arize monitors with type, status (TRIGGERED, CLEARED or NO_DATA), latest computed value and last evaluation time.
  • get_monitor: Get one Arize monitor by id with type, status, latest computed value and dates.
  • list_ai_integrations: List the AI provider integrations configured for evaluators: provider, base URL and model names (keys and headers are not returned).

BYOK key

You bring your own Arize AX Workspace 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

Live from the Arize AX Workspace 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 Workspace. Arize AX Workspace 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 Workspace account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Arize AX organizations, spaces, projects and monitors (BYOK) — Privacy Policy

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

What Arize AX organizations, spaces, projects and monitors (BYOK) is. Arize AX organizations, spaces, projects and monitors (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Arize AX Workspace data: Read your Arize AX organizations, spaces, projects, monitors and AI integration names with your own API key (global API host). You bring your own Arize AX Workspace 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 Workspace 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 Workspace 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 Workspace receives. The request we make on your behalf, including the key and the arguments, under Arize AX Workspace's own terms and privacy policy. Arize AX Workspace 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 Workspace 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 Workspace 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 Workspace (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 Workspace at any time to end all access.

Children. Arize AX organizations, spaces, projects and monitors (BYOK) is a general-audience service operated by the adult using the assistant, under Arize AX Workspace's own age rules.

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

Terms of service

Back to top

Arize AX organizations, spaces, projects and monitors (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Arize AX organizations, spaces, projects and monitors (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Arize AX organizations, spaces, projects and monitors (BYOK) provides: Read your Arize AX organizations, spaces, projects, monitors and AI integration names 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 Workspace credentials and only access data you are allowed to access. Arize AX Workspace's terms apply to your use of Arize AX Workspace; 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 Workspace. Arize AX Workspace 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 Workspace returns, lightly trimmed; it may be incomplete, delayed or changed by Arize AX Workspace. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Arize AX Workspace 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 Workspace'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 Workspace 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 Workspace 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 Workspace 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-workspace

Arize AX organizations, spaces, projects and monitors (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. Arize AX organizations, spaces, projects and monitors (BYOK) never asks for them.

Get Arize AX organizations, spaces, projects and monitors (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Arize AX Workspace Arize API key (user key or service key). Create one at https://arize.com/docs/ax/security-and-settings/api-keys, 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 Arize AX Workspace. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Arize AX Workspace.