arize-ai-provider-integration

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: List all integrations accessible in a space: Filter by name (case-insensitive substring match): Paginate large result sets: Key flags: Response fields: Use this to inspect an integration's full configuration or to confirm its ID after creation. 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. AWS Bedrock uses IAM role-based auth instead of an API key. Provide the ARN of the role Arize should assume: Vertex AI uses GCP service account credentials. Provide the GCP project and region: Capture the returned integration ID (e.g., TGxtSW50ZWdyYXRpb246MTI6YUJjRA== ) — it is needed for evaluator creation and other downstream commands.