arize-ai-provider-integration
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 provider credentials, create integration, list integrations, update credentials, delete integration, or connecting an LLM provider to Arize.
Profile →npx skills add github/awesome-copilot --skill arize-ai-provider-integration --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Arize AI Integration Skill > **`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`. > **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., `openAI`, `anthropic`, `awsBedrock`) - **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
- Concepts
- Prerequisites
- List AI Integrations
- Get a Specific Integration
- Create an AI Integration
- OpenAI
- Anthropic
- Azure OpenAI
- AWS Bedrock
- Vertex AI
- Gemini
- NVIDIA NIM
- Custom (OpenAI-compatible endpoint)
- Supported Providers
ax ai-integrations list --space SPACE ax ai-integrations list --space SPACE --name "openai" Get first page ax ai-integrations list --space SPACE --limit 20 -o json Get next page using cursor from previous response ax ai-integrations list --space SPACE --limit 20 --cursor CURSOR_TOKEN -o json ax ai-integrations get NAME_OR_ID ax ai-integrations get NAME_OR_ID -o json ax ai-integrations get NAME_OR_ID --space SPACE # required when using name instead of ID ax ai-integrations create \
What does the arize-ai-provider-integration skill do?
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 provider credentials, create integration, list integrations, update credentials, delete integration, or connecting an LLM provider to Arize.
How do I install it?
Run `npx skills add github/awesome-copilot --skill arize-ai-provider-integration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.