> ## Documentation Index
> Fetch the complete documentation index at: https://portkey-docs-add-third-party-integration-issues-fixes.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Conductor

> Add usage tracking, cost controls, and security guardrails to Conductor with Portkey

**[Conductor](https://conductor.build)** is a macOS AI coding app built on top of Claude Code. It manages workspaces (git worktrees), sessions, and parallel development environments. Conductor configures providers through environment variables in its **Settings → Providers** panel. Add Portkey to get:

* **1600+ LLMs** through one interface — switch providers by updating environment variables
* **Observability** — track costs, tokens, and latency for every request
* **Reliability** — automatic fallbacks, retries, and caching
* **Governance** — budget limits, usage tracking, and team access controls

<Note>
  For enterprise deployments across teams, see [Enterprise Governance](#3-enterprise-governance).
</Note>

## 1. Setup

<Steps>
  <Step title="Add Provider">
    Go to [Model Catalog](https://app.portkey.ai/model-catalog) → **Add Provider**.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/portkey-docs-add-third-party-integration-issues-fixes/Screenshot2025-07-21at5.29.57PM.png" width="500" />
    </Frame>
  </Step>

  <Step title="Configure Credentials">
    Select provider (OpenAI, Anthropic, etc.), enter API key, and create a slug like `anthropic-prod`.

    <Frame>
      <img src="https://mintcdn.com/portkey-docs-add-third-party-integration-issues-fixes/9m2__JsviRgGAg35/images/product/model-catalog/create-provider-page.png?fit=max&auto=format&n=9m2__JsviRgGAg35&q=85&s=f635c14fcb9a0f4261c853b9497fecea" width="500" data-path="images/product/model-catalog/create-provider-page.png" />
    </Frame>
  </Step>

  <Step title="Get Portkey API Key">
    Go to [API Keys](https://app.portkey.ai/api-keys) and generate your Portkey API key.
  </Step>
</Steps>

## 2. Configure Portkey in Conductor

Conductor sets provider configuration through environment variables in its **Settings → Providers** panel. Since Conductor uses Claude Code under the hood, it accepts the same `ANTHROPIC_*` environment variables.

Set the following variables in **Settings → Providers** under Claude Code:

```bash theme={null}
ANTHROPIC_BASE_URL=https://api.portkey.ai
ANTHROPIC_AUTH_TOKEN=YOUR_PORTKEY_API_KEY
ANTHROPIC_CUSTOM_HEADERS=x-portkey-api-key: YOUR_PORTKEY_API_KEY
ANTHROPIC_CUSTOM_HEADERS=x-portkey-provider: @anthropic-prod
ANTHROPIC_API_KEY=
```

### Choose your provider

The configuration pattern is the same for all providers — only the provider slug and model names change:

<CodeGroup>
  ```bash Anthropic theme={null}
  ANTHROPIC_BASE_URL=https://api.portkey.ai
  ANTHROPIC_AUTH_TOKEN=YOUR_PORTKEY_API_KEY
  ANTHROPIC_CUSTOM_HEADERS=x-portkey-api-key: YOUR_PORTKEY_API_KEY
  ANTHROPIC_CUSTOM_HEADERS=x-portkey-provider: @anthropic-prod
  ANTHROPIC_DEFAULT_SONNET_MODEL=claude-sonnet-4-20250514
  ANTHROPIC_DEFAULT_OPUS_MODEL=claude-opus-4-20250514
  ANTHROPIC_DEFAULT_HAIKU_MODEL=claude-haiku-4-20250514
  ANTHROPIC_API_KEY=
  ```

  ```bash Bedrock theme={null}
  ANTHROPIC_BASE_URL=https://api.portkey.ai
  ANTHROPIC_AUTH_TOKEN=YOUR_PORTKEY_API_KEY
  ANTHROPIC_CUSTOM_HEADERS=x-portkey-api-key: YOUR_PORTKEY_API_KEY
  ANTHROPIC_CUSTOM_HEADERS=x-portkey-provider: @anthropic-prod
  ANTHROPIC_DEFAULT_SONNET_MODEL=us.anthropic.claude-sonnet-4-20250514-v1:0
  ANTHROPIC_DEFAULT_OPUS_MODEL=us.anthropic.claude-opus-4-20250514-v1:0
  ANTHROPIC_DEFAULT_HAIKU_MODEL=us.anthropic.claude-haiku-4-20250514-v1:0
  ANTHROPIC_API_KEY=
  ```

  ```bash Vertex AI theme={null}
  ANTHROPIC_BASE_URL=https://api.portkey.ai
  ANTHROPIC_AUTH_TOKEN=YOUR_PORTKEY_API_KEY
  ANTHROPIC_CUSTOM_HEADERS=x-portkey-api-key: YOUR_PORTKEY_API_KEY\nx-portkey-provider: @vertex-prod
  ANTHROPIC_DEFAULT_SONNET_MODEL=claude-sonnet-4-20250514
  ANTHROPIC_DEFAULT_OPUS_MODEL=claude-opus-4-20250514
  ANTHROPIC_DEFAULT_HAIKU_MODEL=claude-haiku-4-20250514
  ANTHROPIC_API_KEY=
  ```
</CodeGroup>

<Warning>
  **Model names are required.** Each provider uses different model IDs. Without the correct model settings, requests will fail.
</Warning>

Monitor usage in the [Portkey Dashboard](https://app.portkey.ai/dashboard).

## 3. Using Conductor with 1600+ models

With Portkey, you can route Conductor requests to any of 1600+ models. Change the `x-portkey-provider` header to your desired provider slug from [Model Catalog](https://app.portkey.ai/model-catalog).

### Universal provider (any model)

Use Portkey's unified gateway to route to any supported model:

```bash theme={null}
ANTHROPIC_BASE_URL=https://api.portkey.ai
ANTHROPIC_AUTH_TOKEN=YOUR_PORTKEY_API_KEY
ANTHROPIC_CUSTOM_HEADERS=x-portkey-api-key: YOUR_PORTKEY_API_KEY
ANTHROPIC_CUSTOM_HEADERS=x-portkey-provider: @your-provider
ANTHROPIC_MODEL=$YOUR_MODEL
ANTHROPIC_API_KEY=
```

Swap `@your-provider` to any provider slug (e.g., `@openai-prod`, `@xai-prod`, `@moonshot-prod`) and set `ANTHROPIC_MODEL` to your target model ID.

## Why use Portkey with Conductor?

### Cross-provider fallbacks

Never lose a coding session due to provider outages. Configure automatic failover:

```json theme={null}
{
  "strategy": { "mode": "fallback" },
  "targets": [
    { "provider": "@anthropic-prod" },
    { "provider": "@bedrock-prod" },
    { "provider": "@vertex-prod" }
  ]
}
```

### Budget controls for agentic coding

Conductor sessions can run expensive agentic loops. Set hard limits:

* **Cost limits**: Maximum spend per day/week/month
* **Token limits**: Maximum tokens consumed
* **Rate limits**: Requests per minute/hour

### Full session observability

Track every request in your coding session:

* Request/response logs with full context
* Token usage and cost breakdowns
* Latency metrics
* Trace IDs for grouping related requests

### Caching

Reduce costs and latency for repeated queries (common in iterative coding):

```json theme={null}
{
  "cache": { "mode": "simple" }
}
```

## Common configuration

### Forward headers (required)

Some Claude Code features need the `anthropic-beta` header forwarded. Add this to your [Portkey Config](/product/ai-gateway/configs):

```json theme={null}
{
  "provider": "@your-provider-slug",
  "forward_headers": ["anthropic-beta"]
}
```

## Troubleshooting

| Symptom                       | Cause                | Fix                                               |
| ----------------------------- | -------------------- | ------------------------------------------------- |
| `API Error: 500 fetch failed` | Wrong base URL       | Use `https://api.portkey.ai` (no `/v1`)           |
| Lightning symbol (⚡) in logs  | Passthrough request  | Check provider slug and API key                   |
| Requests not appearing        | Authentication issue | Ensure `ANTHROPIC_API_KEY` is set to empty string |

# 3. Set Up Enterprise Governance

**Why Enterprise Governance?**

* **Cost Management**: Controlling and tracking AI spending across teams
* **Access Control**: Managing team access and workspaces
* **Usage Analytics**: Understanding how AI is being used across the organization
* **Security & Compliance**: Maintaining enterprise security standards
* **Reliability**: Ensuring consistent service across all users
* **Model Management**: Managing what models are being used in your setup

Portkey adds a comprehensive governance layer to address these enterprise needs.

**Enterprise Implementation Guide**

<AccordionGroup>
  <Accordion title="Step 1: Implement Budget Controls & Rate Limits">
    ### Step 1: Implement Budget Controls & Rate Limits

    Model Catalog enables you to have granular control over LLM access at the team/department level. This helps you:

    * Set up [budget limits](/product/model-catalog/budget-limits)
    * Prevent unexpected usage spikes using Rate limits
    * Track departmental spending

    #### Setting Up Department-Specific Controls:

    1. Navigate to [Model Catalog](https://app.portkey.ai/model-catalog) in Portkey dashboard
    2. Create new Provider for each engineering team with budget limits and rate limits
    3. Configure department-specific limits

    <Frame>
      <img src="https://mintcdn.com/portkey-docs-add-third-party-integration-issues-fixes/9m2__JsviRgGAg35/images/product/model-catalog/create-provider-page.png?fit=max&auto=format&n=9m2__JsviRgGAg35&q=85&s=f635c14fcb9a0f4261c853b9497fecea" width="500" data-path="images/product/model-catalog/create-provider-page.png" />
    </Frame>
  </Accordion>

  <Accordion title="Step 2: Define Model Access Rules">
    ### Step 2: Define Model Access Rules

    As your AI usage scales, controlling which teams can access specific models becomes crucial. You can simply manage AI models in your org by provisioning model at the top integration level.

    <Frame>
      <img src="https://mintcdn.com/portkey-docs-add-third-party-integration-issues-fixes/9m2__JsviRgGAg35/images/product/model-catalog/model-provisioning-page.png?fit=max&auto=format&n=9m2__JsviRgGAg35&q=85&s=f4b8dca7028bd84504acaf6b663404c5" width="500" data-path="images/product/model-catalog/model-provisioning-page.png" />
    </Frame>
  </Accordion>

  <Accordion title="Step 4: Set Routing Configuration">
    Portkey allows you to control your routing logic very simply with it's Configs feature. Portkey Configs provide this control layer with things like:

    * **Data Protection**: Implement guardrails for sensitive code and data
    * **Reliability Controls**: Add fallbacks, load-balance, retry and smart conditional routing logic
    * **Caching**: Implement Simple and Semantic Caching. and more....

    #### Example Configuration:

    Here's a basic configuration to load-balance requests to OpenAI and Anthropic:

    ```json theme={null}
    {
    	"strategy": {
    		"mode": "load-balance"
    	},
    	"targets": [
    		{
    			"override_params": {
    				"model": "@YOUR_OPENAI_PROVIDER_SLUG/gpt-model"
    			}
    		},
    		{
    			"override_params": {
    				"model": "@YOUR_ANTHROPIC_PROVIDER/claude-sonnet-model"
    			}
    		}
    	]
    }
    ```

    Create your config on the [Configs page](https://app.portkey.ai/configs) in your Portkey dashboard. You'll need the config ID for connecting.

    <Note>
      Configs can be updated anytime to adjust controls without affecting running applications.
    </Note>
  </Accordion>

  <Accordion title="Step 4: Implement Access Controls">
    ### Step 3: Implement Access Controls

    Create User-specific API keys that automatically:

    * Track usage per developer/team with the help of metadata
    * Apply appropriate configs to route requests
    * Collect relevant metadata to filter logs
    * Enforce access permissions

    Create API keys through:

    * [Portkey App](https://app.portkey.ai/)
    * [API Key Management API](/api-reference/admin-api/control-plane/api-keys/create-api-key)

    Example using Python SDK:

    ```python theme={null}
    from portkey_ai import Portkey

    portkey = Portkey(api_key="YOUR_ADMIN_API_KEY")

    api_key = portkey.api_keys.create(
        name="frontend-engineering",
        type="organisation",
        workspace_id="YOUR_WORKSPACE_ID",
        defaults={
            "config_id": "your-config-id",
            "metadata": {
                "environment": "development",
                "department": "engineering",
                "team": "frontend"
            }
        },
        scopes=["logs.view", "configs.read"]
    )
    ```

    For detailed key management instructions, see our [API Keys documentation](/api-reference/admin-api/control-plane/api-keys/create-api-key).
  </Accordion>

  <Accordion title="Step 5: Deploy & Monitor">
    ### Step 4: Deploy & Monitor

    After distributing API keys to your engineering teams, your enterprise-ready setup is ready to go. Each developer can now use their designated API keys with appropriate access levels and budget controls.
    Apply your governance setup using the integration steps from earlier sections
    Monitor usage in Portkey dashboard:

    * Cost tracking by engineering team
    * Model usage patterns for AI agent tasks
    * Request volumes
    * Error rates and debugging logs
  </Accordion>
</AccordionGroup>

<Check>
  ### Enterprise Features Now Available

  **You now have:**

  * Departmental budget controls
  * Model access governance
  * Usage tracking & attribution
  * Security guardrails
  * Reliability features
</Check>

# Portkey Features

Now that you have an enterprise-grade setup, let's explore the comprehensive features Portkey provides to ensure secure, efficient, and cost-effective AI operations.

### 1. Comprehensive Metrics

Using Portkey you can track 40+ key metrics including cost, token usage, response time, and performance across all your LLM providers in real time. You can also filter these metrics based on custom metadata that you can set in your configs. Learn more about metadata here.

<Frame>
  <img src="https://mintcdn.com/portkey-docs-add-third-party-integration-issues-fixes/iw8u5vDH8VX-5kWU/images/integrations/observability.png?fit=max&auto=format&n=iw8u5vDH8VX-5kWU&q=85&s=aff355af05efa0aa0168bde9e5c2de4d" width="600" data-path="images/integrations/observability.png" />
</Frame>

### 2. Advanced Logs

Portkey's logging dashboard provides detailed logs for every request made to your LLMs. These logs include:

* Complete request and response tracking
* Metadata tags for filtering
* Cost attribution and much more...

<Frame>
  <img src="https://mintcdn.com/portkey-docs-add-third-party-integration-issues-fixes/iw8u5vDH8VX-5kWU/images/llms/openai/logs.png?fit=max&auto=format&n=iw8u5vDH8VX-5kWU&q=85&s=2436bacd45bba4732dfb4d19fe806edc" width="3040" height="1764" data-path="images/llms/openai/logs.png" />
</Frame>

### 3. Unified Access to 1600+ LLMs

You can easily switch between 1600+ LLMs. Call various LLMs such as Anthropic, Gemini, Mistral, Azure OpenAI, Google Vertex AI, AWS Bedrock, and many more by simply changing the `provider` slug in your default `config` object.

### 4. Advanced Metadata Tracking

Using Portkey, you can add custom metadata to your LLM requests for detailed tracking and analytics. Use metadata tags to filter logs, track usage, and attribute costs across departments and teams.

<Card title="Custom Metata" icon="coins" href="/product/observability/metadata" />

### 5. Enterprise Access Management

<CardGroup cols={2}>
  <Card title="Budget Controls" icon="coins" href="/product/model-catalog/budget-limits">
    Set and manage spending limits across teams and departments. Control costs with granular budget limits and usage tracking.
  </Card>

  <Card title="Single Sign-On (SSO)" icon="key" href="/product/enterprise-offering/org-management/sso">
    Enterprise-grade SSO integration with support for SAML 2.0, Okta, Azure AD, and custom providers for secure authentication.
  </Card>

  <Card title="Organization Management" icon="building" href="/product/enterprise-offering/org-management">
    Hierarchical organization structure with workspaces, teams, and role-based access control for enterprise-scale deployments.
  </Card>

  <Card title="Access Rules & Audit Logs" icon="shield-check" href="/product/enterprise-offering/access-control-management#audit-logs">
    Comprehensive access control rules and detailed audit logging for security compliance and usage tracking.
  </Card>
</CardGroup>

### 6. Reliability Features

<CardGroup cols={3}>
  <Card title="Fallbacks" icon="life-ring" href="/product/ai-gateway/fallbacks">
    Automatically switch to backup targets if the primary target fails.
  </Card>

  <Card title="Conditional Routing" icon="route" href="/product/ai-gateway/conditional-routing">
    Route requests to different targets based on specified conditions.
  </Card>

  <Card title="Load Balancing" icon="key" href="/product/ai-gateway/load-balancing">
    Distribute requests across multiple targets based on defined weights.
  </Card>

  <Card title="Caching" icon="database" href="/product/ai-gateway/cache-simple-and-semantic">
    Enable caching of responses to improve performance and reduce costs.
  </Card>

  <Card title="Smart Retries" icon="database" href="/product/ai-gateway/automatic-retries">
    Automatic retry handling with exponential backoff for failed requests
  </Card>

  <Card title="Budget Limits" icon="shield-check" href="/product/model-catalog/budget-limits">
    Set and manage budget limits across teams and departments. Control costs with granular budget limits and usage tracking.
  </Card>
</CardGroup>

### 7. Advanced Guardrails

Protect your Project's data and enhance reliability with real-time checks on LLM inputs and outputs. Leverage guardrails to:

* Prevent sensitive data leaks
* Enforce compliance with organizational policies
* PII detection and masking
* Content filtering
* Custom security rules
* Data compliance checks

<Card title="Guardrails" icon="shield-check" href="/product/guardrails">
  Implement real-time protection for your LLM interactions with automatic detection and filtering of sensitive content, PII, and custom security rules. Enable comprehensive data protection while maintaining compliance with organizational policies.
</Card>

# FAQs

<AccordionGroup>
  <Accordion title="How do I update my AI Provider limits after creation?">
    Update AI Provider limits at any time from [Model Catalog](https://app.portkey.ai/model-catalog): 1. Open the provider you want to modify. 2. Update the budget or rate limits. 3. Save your changes.
  </Accordion>

  <Accordion title="Can I use multiple LLM providers with the same API key?">
    Yes! Add multiple AI Providers to Model Catalog (one for each provider) and attach them to a single config. This config can then be connected to your API key, allowing you to use multiple providers through a single API key.
  </Accordion>

  <Accordion title="How do I track costs for different teams?">
    Portkey provides several ways to track team costs:

    * Create separate AI Providers for each team
    * Use metadata tags in your configs
    * Set up team-specific API keys
    * Monitor usage in the analytics dashboard
  </Accordion>

  <Accordion title="What happens if a team exceeds their budget limit?">
    When a team reaches their budget limit:

    1. Further requests will be blocked
    2. Team admins receive notifications
    3. Usage statistics remain available in dashboard
    4. Limits can be adjusted if needed
  </Accordion>
</AccordionGroup>

# Next Steps

**Join our Community**

* [Discord Community](https://portkey.sh/discord-report)
* [GitHub Repository](https://github.com/Portkey-AI)

<Note>
  For enterprise support and custom features, contact our [enterprise team](https://calendly.com/portkey-ai).
</Note>