/arize-experiment

name: arize-experiment
description: Creates, runs, and analyzes Arize experiments for evaluating and comparing model performance. Covers experiment CRUD, exporting runs, comparing results, and evaluation workflows using the ax CLI. Use when the user mentions create experiment, run experiment, compare models, model performance, evaluate AI, experiment results, benchmark, A/B test models, or measure accuracy.
metadata:
  author: arize
  version: "1.0"
compatibility: Requires the ax CLI and a configured Arize profile.

Arize Experiment Skill

> **`SPACE`** — All `--space` flags and the `ARIZE_SPACE` env var accept a space **name** (e.g., `my-workspace`) or a base64 space **ID** (e.g., `U3BhY2U6...`). Find yours with `ax spaces list`.

Concepts

• **Experiment** = a named evaluation run against a specific dataset version, containing one run per example
• **Experiment Run** = the result of processing one dataset example -- includes the model output, optional evaluations, and optional metadata
• **Dataset** = a versioned collection of examples; every experiment is tied to a dataset and a specific dataset version
• **Evaluation** = a named metric attached to a run (e.g., `correctness`, `relevance`), with optional label, score, and explanation

The typical flow: export a dataset → process each example → collect outputs and evaluations → create an experiment with the runs.

Prerequisites

Proceed directly with the task — run the `ax` command you need. Do NOT check versions, env vars, or profiles upfront.

If an `ax` command fails, troubleshoot based on the error:

• `command not found` or version error → see references/ax-setup.md
• `401 Unauthorized` / missing API key → run `ax profiles show` to inspect the current profile. If the profile is missing or the API key is wrong, follow references/ax-profiles.md to create/update it. If the user doesn't have their key, direct them to https://app.arize.com/admin > API Keys
• Space unknown → run `ax spaces list` to pick by name, or ask the user
• Project unclear → ask the user, or run `ax projects list -o json --limit 100` and present as selectable options
• **Security:** Never read `.env` files or search the filesystem for credentials. Use `ax profiles` for Arize credentials and `ax ai-integrations` for LLM provider keys. If credentials are not available through these channels, ask the user.
• **CRITICAL — Never fabricate outputs:** When running an experiment, you MUST call the real model API specified by the user for every dataset example. Never fabricate, simulate, or hardcode model outputs, latencies, or evaluation scores. If you cannot call the API (missing SDK, missing credentials, network error), stop and tell the user what is needed before proceeding.

List Experiments: `ax experiments list`

Browse experiments, optionally filtered by dataset. Output goes to stdout.

ax experiments list
ax experiments list --dataset DATASET_NAME --space SPACE --limit 20   # DATASET_NAME: name or ID (name preferred)
ax experiments list --cursor CURSOR_TOKEN
ax experiments list -o json

Flags

| Flag | Type | Default | Description | |------|------|---------|-------------| | `--dataset` | string | none | Filter by dataset | | `--limit, -l` | int | 15 | Max results (1-100) | | `--cursor` | string | none | Pagination cursor from previous response | | `-o, --output` | string | table | Output format: table, json, csv, parquet, or file path | | `-p, --profile` | string | default | Configuration profile |

Get Experiment: `ax experiments get`

Quick metadata lookup -- returns experiment name, linked dataset/version, and timestamps.

ax experiments get NAME_OR_ID
ax experiments get NAME_OR_ID -o json
ax experiments get NAME_OR_ID --dataset DATASET_NAME --space SPACE   # required when using experiment name instead of ID

Flags

| Flag | Type | Default | Description | |------|------|---------|-------------| | `NAME_OR_ID` | string | required | Experiment name or ID (positional) | | `--dataset` | string | none | Dataset name or ID (required if using experiment name instead of ID) | | `--space` | string | none | Space name or ID (required if using dataset name instead of ID) | | `-o, --output` | string | table | Output format | | `-p, --profile` | string | default | Configuration profile |

Response fields

| Field | Type | Description | |-------|------|-------------| | `id` | string | Experiment ID | | `name` | string | Experiment name | | `dataset_id` | string | Linked dataset ID | | `dataset_version_id` | string | Specific dataset version used | | `experiment_traces_project_id` | string | Project where experiment traces are stored | | `created_at` | datetime | When the experiment was created | | `updated_at` | datetime | Last modification time |

Export Experiment: `ax experiments export`

Download all runs to a file. By default uses the REST API; pass `--all` to use Arrow Flight for bulk transfer.

# EXPERIMENT_NAME, DATASET_NAME: name or ID (name preferred)
ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE
# -> experiment_abc123_20260305_141500/runs.json

ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE --all
ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE --output-dir ./results
ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE --stdout
ax experiments export EXPERIMENT_NAME --dataset DATASET_NAME --space SPACE --stdout | jq '.[0]'

Flags

| Flag | Type | Default | Description | |------|------|---------|-------------| | `NAME_OR_ID` | string | required | Experiment name or ID (positional) | | `--dataset` | string | none | Dataset name or ID (required if using experiment name instead of ID) | | `--space` | string | none | Space name or ID (required if using dataset name instead of ID) | | `--all` | bool | false | Use Arrow Flight for bulk export (see below) | | `--output-dir` | string | `.` | Outpu