• Unified AI Gateway - Single interface for 250+ LLMs with API key management
• Centralized AI observability: Real-time usage tracking for 40+ key metrics and logs for every request
• Governance - Real-time spend tracking, set budget limits and RBAC in your Cline setup
• Security Guardrails - PII detection, content filtering, and compliance controls

​

1. Setting up Portkey

1

Create an Integration

Navigate to the Integrations section on Portkey’s Sidebar. This is where you’ll connect your LLM providers.

1. Find your preferred provider (e.g., OpenAI, Anthropic, etc.)
2. Click Connect on the provider card
3. In the “Create New Integration” window:
   • Enter a Name for reference
   • Enter a Slug for the integration
   • Enter your API Key and other provider specific details for the provider
4. Click Next Step

In your next step you’ll see workspace provisioning options. You can select the default “Shared Team Workspace” if this is your first time OR chose your current one.

2

Configure Models

On the model provisioning page:

• Leave all models selected (or customize)
• Toggle Automatically enable new models if desired

Click Create Integration to complete the integration

3

Copy the Provider Slug

Once your Integration is created:

1. Go to Model Catalog → Models tab
2. Find and click on you your model button (if your model is not visible, you need to edit your integration from the last step)
3. Copy the slug (e.g., @openai-dev/gpt-4o)

We recommend clicking the Run Test Request button on this step to verify your integration. If you see the error: You do not have enough permissions to execute this request, you’ll need to create a User API Key for this step to work properly.You can create one here. You should be able to see simple chat request output on this step.

This is your unique identifier - you’ll need it for the next step. This slug is basically @your-provider-slug/your-model-name

4

Create Default Config

Portkey’s config is a JSON object used to define routing rules for requests to your gateway. You can create these configs in the Portkey app and reference them in requests via the config ID. For this setup, we’ll create a simple config using your provider (OpenAI) and model (gpt-4o).

1. Go to Configs in Portkey dashboard
2. Create new config with:
   Copy

   Ask AI

   {
       "override_params": {
         "model": "@YOUR_SLUG-FROM-LAST_STEP" // example: @openai-test/gpt-4o-mini
       }
   }
   

3. Save and note the Config ID & Name for the next step

5

Configure Portkey API Key

Finally, create a Portkey API key:

1. Go to API Keys in Portkey
2. Create new API key
3. Select the config that you create from previous step
4. Generate and save your API key

Save your API key securely - you’ll need it for Cline integration.

​

2. Integrate Portkey with Cline

​

Opening Cline Settings

1. Open VS Code with Cline installed
2. Press Cmd/Ctrl + Shift + P to open the command palette
3. Search for Cline: Open in new tab
4. Click on the settings gear icon ⚙️ in the Cline tab

​

Method 1: Using Default Config (Recommended)

1. In the Cline settings, navigate to API Configuration
2. Configure the following settings:
   • API Provider: Select OpenAI Compatible
   • Base URL: https://api.portkey.ai/v1
   • API Key: Your Portkey API key from the setup
   • Model ID: dummy (since the model is defined in your Portkey config)

​

Method 2: Using Custom Headers

1. Configure the basic settings as in Method 1:
   • API Provider: OpenAI Compatible
   • Base URL: https://api.portkey.ai/v1
   • API Key: Your Portkey API key (without default config attached to portkey API key, like we did in Step 1)
   • Model ID: Your desired model slug from Step 1 (e.g., @openai-dev/gpt-4o, @anthropic-test/claude-3-opus-20240229)
2. Custom headers give you flexibility to add specific portkey functionality. Add custom headers by clicking “Add Header” and include:

x-portkey-config: YOUR_CONFIG_ID  // For additional config

​

3. Set Up Enterprise Governance for CLine

• 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

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
• Prevent unexpected usage spikes using Rate limits
• Track departmental spending

​

Setting Up Department-Specific Controls:

1. Navigate to Model Catalog in Portkey dashboard
2. Create new Provider for each engineering team with budget limits and rate limits
3. Configure department-specific limits

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.

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:

Copy

Ask AI

{
	"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 in your Portkey dashboard. You’ll need the config ID for connecting to Cline’s setup.

Configs can be updated anytime to adjust controls without affecting running applications.

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
• API Key Management API

Example using Python SDK:

Copy

Ask AI

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.

Step 5: Deploy & Monitor

​

Step 4: Deploy & Monitor

After distributing API keys to your engineering teams, your enterprise-ready Cline 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

​

Portkey Features

​

1. Comprehensive Metrics

​

2. Advanced Logs

• Complete request and response tracking
• Code context and generation metrics
• Developer attribution
• Cost breakdown per coding session

​

3. Unified Access to 250+ LLMs

​

4. Advanced Metadata Tracking

• Language and framework usage
• Code generation vs completion tasks
• Time-of-day productivity patterns
• Project-specific metrics

​

5. Enterprise Access Management

​

6. Reliability Features

​

7. Advanced Guardrails

• Prevent exposure of API keys and secrets
• Block generation of malicious code patterns
• Enforce coding standards and best practices
• Custom security rules for your organization
• License compliance checks

​

FAQs

​

FAQs

​

Next Steps

• Discord Community
• GitHub Repository