arize-ai-provider-integration

1# Arize AI Integration Skill
2 
3> **`SPACE`** — Most `--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`.
4> **Note:** `ai-integrations create` does **not** accept `--space` — AI integrations are account-scoped. Use `--space` only with `list`, `get`, `update`, and `delete`.
5 
6## Concepts
7 
8- **AI Integration** = stored LLM provider credentials registered in Arize; used by evaluators to call a judge model and by other Arize features that need to invoke an LLM on your behalf
9- **Provider** = the LLM service backing the integration (e.g., `openAI`, `anthropic`, `awsBedrock`)
10- **Integration ID** = a base64-encoded global identifier for an integration (e.g., `TGxtSW50ZWdyYXRpb246MTI6YUJjRA==`); required for evaluator creation and other downstream operations
11- **Scoping** = visibility rules controlling which spaces or users can use an integration
12- **Auth type** = how Arize authenticates with the provider: `default` (provider API key), `proxy_with_headers` (proxy via custom headers), or `bearer_token` (bearer token auth)
13 
14## Prerequisites
15 
16Proceed directly with the task — run the `ax` command you need. Do NOT check versions, env vars, or profiles upfront.
17 
18If an `ax` command fails, troubleshoot based on the error:
19- `command not found` or version error → see references/ax-setup.md
20…