📚 Documentation
Quick Links
- Home - Main documentation page
- Quickstart Guide - Get started quickly with Arize Toolkit
- CLI Reference - Command-line interface documentation
Tools Documentation
| Tool Category | Description |
|---|---|
| Project/Model Tools | Access and manage projects/models, retrieve performance metrics and traces/inference volumes |
| Monitor Tools | Create, copy, and manage monitors and alerting |
| Custom Metrics Tools | Create and manage custom metrics |
| Language Model Tools | Work with prompts, annotations, evaluations, and LLM features |
| Space & Organization Tools | Navigate and manage spaces, organizations, and projects |
| Data Import Tools | Import data from cloud storage and databases |
| Dashboard Tools | Create and manage dashboards |
| Utility Tools | Client configuration and utility functions |
Extensions
| Extension | Description |
|---|---|
| Prompt Optimization | Automated prompt improvement based on historical performance |
For Developers
- Development Guide - Information about extending the toolkit
- Integration Tests - Running integration tests
- Claude Code Skills - AI-assisted development workflows
Claude Code Skills
This repository includes Claude Code skills for AI-assisted development:
| Skill | Description |
|---|---|
arize-graphql-analytics |
Query and explore the Arize GraphQL API, build and validate queries |
new-query-workflow |
Complete workflow for adding new queries/mutations with models, types, tests, and docs |
Use /arize-graphql-analytics or /new-query-workflow in Claude Code to invoke these skills.
Disclaimer
Although this package is used for development work with and within the Arize platform, it is not an Arize product. It is a open source project developed and maintained by an Arize Engineer. Feel free to add issues or reach out for help in the Arize community Slack channel.
Overview
Arize Toolkit is a set of tools packaged as a Python client that lets you easily interact with Arize AI APIs. Here's a quick overview of the main features in the current release:
- Access and manage models
- Retrieve performance metrics over a time period
- Retrieve inference volume over a time period
- Create, copy, and manage custom metrics
- Create, copy, and manage monitors and alerting
- Work with LLM features like prompts and annotations
- Import data from cloud storage (S3, GCS, Azure) and databases (BigQuery, Snowflake, Databricks)
- Create, update, and delete data import jobs with full lifecycle management
- Prompt Optimization Extension (optional): Automatically optimize prompts using meta-prompt techniques with feedback from evaluators
- Command-Line Interface (optional): Manage all Arize resources directly from the terminal with Rich table output and JSON mode
Installation
pip install arize_toolkit
Optional Dependencies
Command-Line Interface
To use the arize_toolkit CLI, install with the cli extras:
pip install arize_toolkit[cli]
Prompt Optimization Extension
For automated prompt optimization using meta-prompt techniques, install with the prompt_optimizer extras:
pip install arize_toolkit[prompt_optimizer]
Command-Line Interface
The CLI wraps all Client functionality so you can manage models, monitors, prompts, and more directly from the terminal.
Quick Start
# One-time setup — saves credentials to ~/.arize_toolkit/config.toml
arize_toolkit config init
# List models (Rich table output by default)
arize_toolkit models list
# Same thing, using the "projects" alias
arize_toolkit projects list
# JSON output, pipe to jq
arize_toolkit --json models list | jq '.[].name'
# Get monitor details for a specific model
arize_toolkit monitors get "accuracy-alert" --model "fraud-detection-v3"
# Create a performance monitor
arize_toolkit monitors create-performance "accuracy-alert" \
--model "fraud-detection-v3" \
--environment production \
--performance-metric accuracy \
--threshold 0.95
# Use a named profile for a different environment
arize_toolkit --profile staging spaces list
Global Options
| Flag | Description |
|---|---|
--version |
Show the installed version |
--profile NAME |
Use a named configuration profile |
--json |
Output raw JSON instead of Rich tables |
--api-key KEY |
Override the API key |
--org NAME |
Override the organization |
--space NAME |
Override the space |
--app-url URL |
Override the Arize app URL |
Command Groups
| Group | Description |
|---|---|
config |
Manage configuration profiles (init, list, show, use) |
spaces |
List, create, and switch spaces |
orgs |
List and create organizations |
users |
Search users and manage space membership |
models / projects |
List models, check volume, pull performance metrics |
monitors |
Create, list, copy, and delete monitors |
prompts |
Manage prompt templates and versions |
custom-metrics |
Create and manage custom metrics |
evaluators |
Manage LLM and code evaluators |
dashboards |
Create and view dashboards |
imports |
Manage file and table import jobs |
See the full CLI documentation for detailed usage and examples.
Client Setup
The Client class is the entrypoint for interacting with the toolkit. It provides maintains the connection information for making requests to the Arize APIs, and offers a wide range of operations for interacting with models, monitors, dashboards, and more.
API Key
To create a client, you need to provide your Arize API key. Use this reference to get your API key from the Arize UI.
Organization and Space
You will also need to provide an organization name and space name. To give some context, models are scoped to a space, and the space is scoped to an organization. These can be found by navigating to the Arize UI and looking at the upper left dropdown from the landing page. You will first select an organization from the dropdown and then pick the space from the available spaces in that organization.
For the example below, the organization is Demo Org and the space is Test Space.
For On Prem deployments
For SaaS users, the default API endpoint is always going to be https://api.arize.com.
If you are using an on prem deployment of Arize, you will need to provide the api_url parameter.
This parameters should just be the base url of your Arize instance.
Metadata
Release files for arize_toolkit 1.0.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| arize_toolkit-1.0.11.tar.gz | 3.8 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| arize_toolkit-1.0.11-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.9 MB
Release files / arize_toolkit-1.0.11.tar.gz
| Download URL | arize_toolkit-1.0.11.tar.gz |
|---|---|
| Size | 3.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e8549d21cba6a5e2ca1a6a0b98b312189dcb987eb0c74cda70a545ee6488c34f
|
|
BLAKE2b-256 checksum How to use checksums |
f5caddf41b23994bc52ee2aad5401c1158789f8b886d0b33365542e0cc2fd035
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.6 {"installer":{"name":"uv","version":"0.10.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / arize_toolkit-1.0.11-py3-none-any.whl
| Download URL | arize_toolkit-1.0.11-py3-none-any.whl |
|---|---|
| Size | 100.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
33554403f14d9318a7c3e60d7b2c2c083c8002373bcf08a320f57a5982268fae
|
|
BLAKE2b-256 checksum How to use checksums |
736e9bd61a705c3093e5e0537e1ce6c89a8b1b1de498d61e94dd146a7cc19680
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.6 {"installer":{"name":"uv","version":"0.10.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for arize_toolkit 1.0.11
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.