Creates, reads, updates, and deletes Arize AI integrations that store LLM provider credentials used by evaluators and other Arize features. Supports any LLM provider (e.g. OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Vertex AI, Gemini, NVIDIA NIM). Use when the user mentions AI integration, LLM pro

Arize AI Integration Skill SPACE — space flags accept a space name (e.g., my workspace ) or a base64 space ID (e.g., U3BhY2U6... ). Find yours with ax spaces list . Note: ai integrations create does not accept space — AI integrations are account scoped. Use space only with list , get , update , and delete . Concepts 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 Provider = the LLM service backing the integration (e.g., OPEN AI , ANTHROPIC , AWS BEDROCK ) Integration ID = a base64 encoded global identifier for an integration (e.g., TGxtSW50ZWdyYXRpb246MTI6YUJjRA== ); required for evaluator creation and other downstream operations Scoping = visibility rules controlling which spaces or users can use an integration 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) 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](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](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 LLM provider call fails (missing provider credentials) → run ax ai integrations list space SPACE to check for platform managed credentials. If none exist: Preferred: Give the user the exact ax ai integrations create command from Supported Providers below (reference env var names like $OPENAI API KEY , never raw values). Ask them to export the provider key in their own terminal and run the command there — never paste the key into chat. Do not run the create command yourself unless the var is already exported in this terminal session. Bedrock/Vertex: use provider metadata instead of api key (see Supported Providers below). 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. Never ask the user to paste secrets into chat. For missing credentials, see [references/ax profiles.md](references/ax profiles.md). List AI Integrations List all integrations accessible in a space: Filter by name (case insensitive substring match): Paginate large result sets: Key flags: Flag Description space Space name or ID to filter integrations name Case insensitive substring filter on integration name limit Max results (1–100, default 15) cursor Pagination token from a previous response o, output Output format: table (default) or json Response fields: Field Description id Base64 integration ID — copy this for downstream commands name Human readable name provider LLM provider enum (see Supported Providers below) has api key true if credentials are stored model names Allowed model list, or null if all models are enabled enable default models Whether default models for this provider are allowed function calling enabled Whether tool/function calling is enabled auth type Authentication method: DEFAULT , PROXY WITH HEADERS , or BEARER TOKEN Get a Specific Integration Use this to inspect an integration's full configuration or to confirm its ID after creation. Create an AI Integration Before creating, always list integrations first — the user may already have a suitable one: If no suitable integration exists, create one. The required flags depend on the provider. OpenAI Anthropic Azure OpenAI AWS Bedrock AWS Bedrock uses IAM role based auth. Provide the ARN of the role Arize should assume via provider metadata : Vertex AI Vertex AI uses GCP service account credentials. Provide the GCP project and region via provider metadata : Gemini NVIDIA NIM Custom (OpenAI compatible endpoint) LiteLLM Supported Providers Provider Required extra flags OPEN AI api key <key ANTHROPIC api key <key AZURE OPEN AI api key <key , base url <azure endpoint AWS BEDROCK provider metadata '{"role arn": "<arn "}' VERTEX AI provider metadata '{"project id": "<gcp project ", "location": "<region ", "project access label": "<label "}' GEMINI api key <key NVIDIA NIM api key <key , base url <nim endpoint CUSTOM base url <endpoint LITELLM base url <endpoint Optional flags for any provider Flag Description model name Allowed model name (repeat for multiple, e.g. model name gpt 4o model name gpt 4o mini ); omit to allow all models enable default models Enable the provider's default model list function calling enabled Enable tool/function calling support auth type Authentication type: DEFAULT , PROXY WITH HEADERS , BEARER TOKEN , or OAUTH2 CLIENT CREDENTIALS headers Custom headers as JSON object or file path (for proxy auth) provider metadata Provider specific metadata as JSON object or file path After creation Capture the returned integration ID (e.g., TGxtSW50ZWdyYXRpb246MTI6YUJjRA== ) — it is needed for evaluator creation and other downstream commands. If you missed it, retrieve it: Update an AI Integration update is a partial update — only the flags you provide are changed. Omitted fields stay as is. Add space SPACE when using a name instead of ID. Any flag accepted by create can be passed to update . scopings flag: Controls which spaces can use this integration. Accepts a JSON array of scoping rules. Replaces all existing scopings on update. Use ax spaces list o json to find space global IDs. Delete an AI Integration Warning: Deletion is permanent. Evaluators that reference this integration will no longer be able to run. Omit force to get a confirmation prompt instead of deleting immediately. Troubleshooting Problem Solution ax: command not found See [references/ax setup.md](references/ax setup.md) 401 Unauthorized API key may not have access to this space. Verify key and space ID at https://app.arize.com/admin API Keys No profile found Run ax profiles show expand ; set ARIZE API KEY env var or write ~/.arize/config.toml Integration not found Verify with ax ai integrations list space SPACE has api key: false after create Credentials were not saved — re run update with the correct api key or provider metadata Evaluator runs fail with LLM errors Check integration credentials with ax ai integrations get INT ID ; rotate the API key if needed provider mismatch Cannot change provider after creation — delete and recreate with the correct provider Related Skills arize evaluator : Create LLM as judge evaluators that use an AI integration → use arize evaluator arize experiment : Run experiments that use evaluators backed by an AI integration → use arize experiment Save Credentials for Future Use See [references/ax profiles.md](references/ax profiles.md) § Save Credentials for Future Use.

arize-ai-provider-integration