OpenAI Agents SDK (TypeScript)

Introduction

OpenAI Agents SDK enables the development of complex AI agents with tools, planning, and memory capabilities. Portkey enhances OpenAI Agents with observability, reliability, and production-readiness features. Portkey turns your experimental OpenAI Agents into production-ready systems by providing:

Complete observability of every agent step, tool use, and interaction
Built-in reliability with fallbacks, retries, and load balancing
Cost tracking and optimization to manage your AI spend
Access to 1600+ LLMs through a single integration
Guardrails to keep agent behavior safe and compliant
Version-controlled prompts for consistent agent performance

OpenAI Agents SDK Official Documentation

Learn more about OpenAI Agents SDK’s core concepts

Installation & Setup

Install the required packages

npm install @openai/agents portkey-ai

Generate API Key

Create a Portkey API key with optional budget/rate limits and attach your Config

Connect to OpenAI Agents

There are 3 ways to integrate Portkey with OpenAI Agents:

Set a client that applies to all agents in your application
Use a custom provider for selective Portkey integration
Configure each agent individually

See the Integration Approaches section for more details.

Configure Portkey Client

For a simple setup, we’ll use the global client approach:

import { Agent, run } from '@openai/agents';
import { setDefaultOpenAIClient, setOpenAIAPI, setTracingDisabled } from '@openai/agents';
import { OpenAI } from 'openai';
import { PORTKEY_GATEWAY_URL, createHeaders } from 'portkey-ai';

// Set up Portkey as the global client
const portkey = new OpenAI({
    baseURL: PORTKEY_GATEWAY_URL,
    apiKey: process.env.PORTKEY_API_KEY!,
    defaultHeaders: createHeaders({
        provider:"@YOUR_OPENAI_PROVIDER"
    })
});

// Register as the SDK-wide default
setDefaultOpenAIClient(portkey);
setOpenAIAPI('chat_completions');  // Responses API → Chat
setTracingDisabled(true);           // Optional: disable OpenAI's tracing

Getting Started

Let’s create a simple question-answering agent with OpenAI Agents SDK and Portkey. This agent will respond directly to user messages using a language model:

import { Agent, run } from '@openai/agents';
import { setDefaultOpenAIClient, setOpenAIAPI, setTracingDisabled } from '@openai/agents';
import { OpenAI } from 'openai';
import { PORTKEY_GATEWAY_URL, createHeaders } from 'portkey-ai';

// Set up Portkey as the global client
const portkey = new OpenAI({
    baseURL: PORTKEY_GATEWAY_URL,
    apiKey: process.env.PORTKEY_API_KEY!,
    defaultHeaders: createHeaders({
        provider:"@YOUR_OPENAI_PROVIDER"
    })
});

// Register as the SDK-wide default
setDefaultOpenAIClient(portkey);
setOpenAIAPI('chat_completions');  // Responses API → Chat
setTracingDisabled(true);           // Optional: disable OpenAI's tracing

// Create agent with any supported model
const agent = new Agent({
    name: "Assistant",
    instructions: "You are a helpful assistant.",
    model: "gpt-4o"
});

// Run the agent
const result = await run(agent, "Tell me about quantum computing.");
console.log(result.finalOutput);

In this example:

We set up Portkey as the global client for OpenAI Agents SDK
We create a simple agent with instructions and a model
We run the agent with a user query
We print the final output

Visit your Portkey dashboard to see detailed logs of this agent’s execution!

End-to-End Example

Research Agent with Tools: Here’s a more comprehensive agent that can use tools to perform tasks.

import { Agent, run, tool } from '@openai/agents';
import { setDefaultOpenAIClient } from '@openai/agents';
import { OpenAI } from 'openai';
import { PORTKEY_GATEWAY_URL, createHeaders } from 'portkey-ai';
import { z } from 'zod';

// Configure Portkey client
const portkey = new OpenAI({
    apiKey: process.env.PORTKEY_API_KEY!,
    baseURL: PORTKEY_GATEWAY_URL,
    defaultHeaders: createHeaders({
        provider:"@YOUR_OPENAI_PROVIDER"
    })
});
setDefaultOpenAIClient(portkey);

// Define agent tools using the tool() helper
const getWeatherTool = tool({
    name: 'get_weather',
    description: 'Get the current weather for a given city',
    parameters: z.object({
        city: z.string(),
        unit: z.enum(['celsius', 'fahrenheit']).nullable().optional()
    }),
    async execute({ city, unit = 'fahrenheit' }) {
        return `The weather in ${city} is 72°${unit === 'celsius' ? 'C' : 'F'} and sunny.`;
    }
});

const searchWebTool = tool({
    name: 'search_web',
    description: 'Search the web for information',
    parameters: z.object({
        query: z.string()
    }),
    async execute({ query }) {
        return `Found information about: ${query}`;
    }
});

// Create agent with tools
const agent = new Agent({
    name: "Research Assistant",
    instructions: "You are a helpful assistant that can search for information and check the weather.",
    model: "gpt-4o",
    tools: [getWeatherTool, searchWebTool]
});

// Run the agent
const result = await run(
    agent,
    "What's the weather in San Francisco and find information about Golden Gate Bridge?"
);
console.log(result.finalOutput);

Visit your Portkey dashboard to see the complete execution flow visualized!

Production Features

1. Enhanced Observability

Portkey provides comprehensive observability for your OpenAI Agents, helping you understand exactly what’s happening during each execution.

Traces
Logs
Metrics & Dashboards
Metadata Filtering

Traces provide a hierarchical view of your agent’s execution, showing the sequence of LLM calls, tool invocations, and state transitions.

// Add tracing to your OpenAI Agents
const portkey = new OpenAI({
    baseURL: PORTKEY_GATEWAY_URL,
    apiKey: process.env.PORTKEY_API_KEY!,
    defaultHeaders: createHeaders({
        traceId: "unique_execution_trace_id", // Add unique trace ID
        provider:"@YOUR_OPENAI_PROVIDER"
    })
});
setDefaultOpenAIClient(portkey);

Add custom metadata to your OpenAI agent calls to enable powerful filtering and segmentation:

// Add metadata to your OpenAI Agents
const portkey = new OpenAI({
    baseURL: PORTKEY_GATEWAY_URL,
    apiKey: process.env.PORTKEY_API_KEY!,
    defaultHeaders: createHeaders({
        metadata: {"agent_type": "research_agent"}, // Add custom metadata
        provider:"@YOUR_OPENAI_PROVIDER"
    })
});
setDefaultOpenAIClient(portkey);

This metadata can be used to filter logs, traces, and metrics on the Portkey dashboard, allowing you to analyze specific agent runs, users, or environments.

2. Reliability - Keep Your Agents Running Smoothly

When running agents in production, things can go wrong - API rate limits, network issues, or provider outages. Portkey’s reliability features ensure your agents keep running smoothly even when problems occur. It’s this simple to enable fallback in your OpenAI Agents:

import { createHeaders, PORTKEY_GATEWAY_URL } from 'portkey-ai';
import { OpenAI } from 'openai';
import { setDefaultOpenAIClient } from '@openai/agents';

// Create a config with fallbacks, It's recommended that you create the Config in Portkey App rather than hard-code the config JSON directly
const config = {
  "strategy": {
    "mode": "fallback"
  },
  "targets": [
    {
      "provider": "openai",
      "override_params": {"model": "gpt-4o"}
    },
    {
      "provider": "anthropic",
      "override_params": {"model": "claude-3-opus-20240229"}
    }
  ]
};

// Configure Portkey client with fallback config
const portkey = new OpenAI({
    baseURL: PORTKEY_GATEWAY_URL,
    apiKey: process.env.PORTKEY_API_KEY!,
    defaultHeaders: createHeaders({
        config: config
    })
});
setDefaultOpenAIClient(portkey);

This configuration will automatically try Claude if the GPT-4o request fails, ensuring your agent can continue operating.

Automatic Retries

Handles temporary failures automatically. If an LLM call fails, Portkey will retry the same request for the specified number of times - perfect for rate limits or network blips.

Request Timeouts

Prevent your agents from hanging. Set timeouts to ensure you get responses (or can fail gracefully) within your required timeframes.

Conditional Routing

Send different requests to different providers. Route complex reasoning to GPT-4, creative tasks to Claude, and quick responses to Gemini based on your needs.

Fallbacks

Keep running even if your primary provider fails. Automatically switch to backup providers to maintain availability.

Load Balancing

Spread requests across multiple API keys or providers. Great for high-volume agent operations and staying within rate limits.

3. Prompting in OpenAI Agents

Portkey’s Prompt Engineering Studio helps you create, manage, and optimize the prompts used in your OpenAI Agents. Instead of hardcoding prompts or instructions, use Portkey’s prompt rendering API to dynamically fetch and apply your versioned prompts.

Prompt Playground
Using Prompt Templates
Prompt Versioning
Mustache Templating for variables

Prompt Playground is a place to compare, test and deploy perfect prompts for your AI application. It’s where you experiment with different models, test variables, compare outputs, and refine your prompt engineering strategy before deploying to production. It allows you to:

Iteratively develop prompts before using them in your agents
Test prompts with different variables and models
Compare outputs between different prompt versions
Collaborate with team members on prompt development

This visual environment makes it easier to craft effective prompts for each step in your OpenAI Agents agent’s workflow.

The Prompt Render API retrieves your prompt templates with all parameters configured:

import { OpenAI } from 'openai';
import { Portkey } from 'portkey-ai';
import { PORTKEY_GATEWAY_URL, createHeaders } from 'portkey-ai';
import { Agent, run, setDefaultOpenAIClient } from '@openai/agents';

// Initialize Portkey client
const portkeyClient = new Portkey({
    apiKey: process.env.PORTKEY_API_KEY!
});

// Retrieve prompt using the render API
const promptData = await portkeyClient.prompts.render({
    promptId: "YOUR_PROMPT_ID",
    variables: {
        user_input: "Tell me about artificial intelligence"
    }
});

// Configure OpenAI client with Portkey
const openaiClient = new OpenAI({
    baseURL: PORTKEY_GATEWAY_URL,
    apiKey: process.env.PORTKEY_API_KEY!,
    defaultHeaders: createHeaders({
        provider:"@YOUR_OPENAI_PROVIDER"
    })
});
setDefaultOpenAIClient(openaiClient);

// Use the rendered prompt in your OpenAI Agent
const agent = new Agent({
    name: "Assistant",
    instructions: promptData.data.messages[0].content, // Use the rendered prompt as instructions
    model: "gpt-4o"
});

const result = await run(agent, "Tell me about artificial intelligence");
console.log(result.finalOutput);

You can:

Create multiple versions of the same prompt
Compare performance between versions
Roll back to previous versions if needed
Specify which version to use in your code:

// Use a specific prompt version
const promptData = await portkeyClient.prompts.render({
    promptId: "YOUR_PROMPT_ID@version_number",
    variables: {
        user_input: "Tell me about quantum computing"
    }
});

Portkey prompts use Mustache-style templating for easy variable substitution:

You are an AI assistant helping with {{task_type}}.

User question: {{user_input}}

Please respond in a {{tone}} tone and include {{required_elements}}.

When rendering, simply pass the variables:

const promptData = await portkeyClient.prompts.render({
    promptId: "YOUR_PROMPT_ID",
    variables: {
        task_type: "research",
        user_input: "Tell me about quantum computing",
        tone: "professional",
        required_elements: "recent academic references"
    }
});

Prompt Engineering Studio

Learn more about Portkey’s prompt management features

4. Guardrails for Safe Agents

Guardrails ensure your OpenAI Agents operate safely and respond appropriately in all situations. Why Use Guardrails? OpenAI Agents can experience various failure modes:

Generating harmful or inappropriate content
Leaking sensitive information like PII
Hallucinating incorrect information
Generating outputs in incorrect formats

Portkey’s guardrails protect against these issues by validating both inputs and outputs. Implementing Guardrails

import { createHeaders, PORTKEY_GATEWAY_URL } from 'portkey-ai';
import { OpenAI } from 'openai';
import { setDefaultOpenAIClient } from '@openai/agents';

// Create a config with input and output guardrails, It's recommended you create Config in Portkey App and pass the config ID in the client
const config = {
    "provider":"@openai-xxx",
    "input_guardrails": ["guardrails-id-xxx", "guardrails-id-yyy"],
    "output_guardrails": ["guardrails-id-xxx"]
};

// Configure OpenAI client with guardrails
const portkey = new OpenAI({
    baseURL: PORTKEY_GATEWAY_URL,
    apiKey: process.env.PORTKEY_API_KEY!,
    defaultHeaders: createHeaders({
        config: config,
        provider:"@YOUR_OPENAI_PROVIDER"
    })
});
setDefaultOpenAIClient(portkey);

Portkey’s guardrails can:

Detect and redact PII in both inputs and outputs
Filter harmful or inappropriate content
Validate response formats against schemas
Check for hallucinations against ground truth
Apply custom business logic and rules

Learn More About Guardrails

Explore Portkey’s guardrail features to enhance agent safety

5. User Tracking with Metadata

Track individual users through your OpenAI Agents using Portkey’s metadata system. What is Metadata in Portkey? Metadata allows you to associate custom data with each request, enabling filtering, segmentation, and analytics. The special _user field is specifically designed for user tracking.

import { createHeaders, PORTKEY_GATEWAY_URL } from 'portkey-ai';
import { OpenAI } from 'openai';
import { setDefaultOpenAIClient } from '@openai/agents';

// Configure client with user tracking
const portkey = new OpenAI({
    baseURL: PORTKEY_GATEWAY_URL,
    apiKey: process.env.PORTKEY_API_KEY!,
    defaultHeaders: createHeaders({
        provider:"@YOUR_LLM_PROVIDER",
        metadata: {
            "_user": "user_123", // Special _user field for user analytics
            "user_name": "John Doe",
            "user_tier": "premium",
            "user_company": "Acme Corp"
        }
    })
});
setDefaultOpenAIClient(portkey);

Filter Analytics by User With metadata in place, you can filter analytics by user and analyze performance metrics on a per-user basis:

This enables:

Per-user cost tracking and budgeting
Personalized user analytics
Team or organization-level metrics
Environment-specific monitoring (staging vs. production)

Learn More About Metadata

Explore how to use custom metadata to enhance your analytics

6. Caching for Efficient Agents

Implement caching to make your OpenAI Agents agents more efficient and cost-effective:

Simple Caching
Semantic Caching

const portkeyConfig = {
  "cache": {
    "mode": "simple"
  },
  "provider":"@YOUR_LLM_PROVIDER"
};

// Configure OpenAI client with chosen provider
const portkey = new OpenAI({
    baseURL: PORTKEY_GATEWAY_URL,
    apiKey: process.env.PORTKEY_API_KEY!,
    defaultHeaders: createHeaders({
        config: portkeyConfig
    })
});
setDefaultOpenAIClient(portkey);

Simple caching performs exact matches on input prompts, caching identical requests to avoid redundant model executions.

const portkeyConfig = {
  "cache": {
    "mode": "semantic"
  },
  "provider":"@YOUR_LLM_PROVIDER"
};

// Configure OpenAI client with chosen provider
const portkey = new OpenAI({
    baseURL: PORTKEY_GATEWAY_URL,
    apiKey: process.env.PORTKEY_API_KEY!,
    defaultHeaders: createHeaders({
        config: portkeyConfig
    })
});
setDefaultOpenAIClient(portkey);

Semantic caching considers the contextual similarity between input requests, caching responses for semantically similar inputs.

7. Model Interoperability

With Portkey, you can easily switch between different LLMs in your OpenAI Agents without changing your core agent logic.

// Configure Portkey with different LLM providers
import { createHeaders, PORTKEY_GATEWAY_URL } from 'portkey-ai';
import { OpenAI } from 'openai';
import { setDefaultOpenAIClient, Agent, run } from '@openai/agents';

// Using OpenAI
const openaiConfig = {
    "provider": "@openai-prod",
    "override_params": {"model": "gpt-4o"}
};

// Using Anthropic
const anthropicConfig = {
    "provider": "@anthropic-prod",
    "override_params": {"model": "claude-3-5-sonnet-latest"}
};

// Choose which config to use
const activeConfig = openaiConfig;  // or anthropicConfig

// Configure OpenAI client with chosen provider
const portkey = new OpenAI({
    baseURL: PORTKEY_GATEWAY_URL,
    apiKey: process.env.PORTKEY_API_KEY!,
    defaultHeaders: createHeaders({
        config: activeConfig
    })
});
setDefaultOpenAIClient(portkey);

// Create and run agent - no changes needed in agent code
const agent = new Agent({
    name: "Assistant",
    instructions: "You are a helpful assistant.",
    // The model specified here will be used as a reference but the actual model
    // is determined by the activeConfig
    model: "gpt-4o"
});

const result = await run(agent, "Tell me about quantum computing.");
console.log(result.finalOutput);

Portkey provides access to over 200 LLMs through a unified interface, including:

OpenAI (GPT-4o, GPT-4 Turbo, etc.)
Anthropic (Claude 3.5 Sonnet, Claude 3 Opus, etc.)
Mistral AI (Mistral Large, Mistral Medium, etc.)
Google Vertex AI (Gemini 1.5 Pro, etc.)
Cohere (Command, Command-R, etc.)
AWS Bedrock (Claude, Titan, etc.)
Local/Private Models

Supported Providers

See the full list of LLM providers supported by Portkey

Set Up Enterprise Governance for OpenAI Agents

Why Enterprise Governance? If you are using OpenAI Agents inside your orgnaization, you need to consider several governance aspects:

Cost Management: Controlling and tracking AI spending across teams
Access Control: Managing which teams can use specific models
Usage Analytics: Understanding how AI is being used across the organization
Security & Compliance: Maintaining enterprise security standards
Reliability: Ensuring consistent service across all users

Portkey adds a comprehensive governance layer to address these enterprise needs. Let’s implement these controls step by step. Enterprise Implementation Guide Portkey allows you to use 1600+ LLMs with your OpenAI Agents setup, with minimal configuration required. Let’s set up the core components in Portkey that you’ll need for integration.

Add an AI Provider

Add your LLM provider credentials to Model Catalog. This gives you centralized control with:

Budget limits per provider
Rate limiting capabilities
Secure credential storage

Go to Model Catalog in the Portkey App and add your provider. Copy the AI Provider slug — you’ll need it for the next step.

Create Default Config

Configs in Portkey are JSON objects that define how your requests are routed. They help with implementing features like advanced routing, fallbacks, and retries.We need to create a default config to route our requests to the AI Provider added in Step 1.To create your config:

Go to Configs in Portkey dashboard

Create new config with:

{
    "provider":"@YOUR_PROVIDER_FROM_STEP1",
   	"override_params": {
      "model": "gpt-4o" // Your preferred model name
    }
}

Save and note the Config name for the next step

This basic config connects to your AI Provider. You can add more advanced Portkey features later.

Configure Portkey API Key

Now create Portkey API key access point and attach the config you created in Step 2:

Go to API Keys in Portkey and Create new API key
Select your config from Step 2
Generate and save your API key

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

Once you have created your API Key after attaching default config, you can directly pass the API key + base URL in the OpenAI client. Here’s how:

import { createHeaders, PORTKEY_GATEWAY_URL } from 'portkey-ai';
import { OpenAI } from 'openai';

const client = new OpenAI({
    apiKey: "YOUR_PORTKEY_API_KEY", // Your Portkey API Key from Step 3
    baseURL: PORTKEY_GATEWAY_URL
});

// your rest of the code remains same

Step 1: Implement Budget Controls & Rate Limits

AI Providers in Model Catalog enable 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:

Navigate to Model Catalog in the Portkey dashboard
Add an AI Provider for each department with budget limits and rate limits
Configure department-specific limits

Step 2: Define Model Access Rules

As your AI usage scales, controlling which teams can access specific models becomes crucial. Portkey Configs provide this control layer with features like:

Access Control Features:

Model Restrictions: Limit access to specific models
Data Protection: Implement guardrails for sensitive data
Reliability Controls: Add fallbacks and retry logic

Example Configuration:

Here’s a basic configuration to route requests to OpenAI, specifically using GPT-4o:

{
	"strategy": {
		"mode": "single"
	},
	"targets": [
		{
			"provider":"@YOUR_OPENAI_PROVIDER",
			"override_params": {
				"model": "gpt-4o"
			}
		}
	]
}

Create your config on the Configs page in your Portkey dashboard. You’ll need the config ID for connecting to OpenAI Agents’s setup.

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

Step 3: Implement Access Controls

Create User-specific API keys that automatically:

Track usage per user/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:

Example using TypeScript SDK:

import { Portkey } from 'portkey-ai';

const portkey = new Portkey({
    apiKey: "YOUR_ADMIN_API_KEY"
});

const apiKey = await portkey.apiKeys.create({
    name: "engineering-team",
    type: "organisation",
    workspaceId: "YOUR_WORKSPACE_ID",
    defaults: {
        configId: "your-config-id",
        metadata: {
            environment: "production",
            department: "engineering"
        }
    },
    scopes: ["logs.view", "configs.read"]
});

For detailed key management instructions, see our API Keys documentation.

Step 4: Deploy & Monitor

After distributing API keys to your team members, your enterprise-ready OpenAI Agents setup is ready to go. Each team member 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 department
Model usage patterns
Request volumes
Error rates

Enterprise Features Now Available

OpenAI Agents now has:

Departmental budget controls
Model access governance
Usage tracking & attribution
Security guardrails
Reliability features

Frequently Asked Questions

How does Portkey enhance OpenAI Agents?

Portkey adds production-readiness to OpenAI Agents through comprehensive observability (traces, logs, metrics), reliability features (fallbacks, retries, caching), and access to 1600+ LLMs through a unified interface. This makes it easier to debug, optimize, and scale your agent applications.

Can I use Portkey with existing OpenAI Agents?

Yes! Portkey integrates seamlessly with existing OpenAI Agents. You only need to replace your client initialization code with the Portkey-enabled version. The rest of your agent code remains unchanged.

Does Portkey work with all OpenAI Agents features?

Portkey supports all OpenAI Agents SDK features, including tool use, memory, planning, and more. It adds observability and reliability without limiting any of the SDK’s functionality.

How does Portkey handle streaming in OpenAI Agents?

Portkey fully supports streaming responses in OpenAI Agents. You can enable streaming by using the appropriate methods in the OpenAI Agents SDK, and Portkey will properly track and log the streaming interactions.

How do I filter logs and traces for specific agent runs?

Portkey allows you to add custom metadata to your agent runs, which you can then use for filtering. Add fields like agent_name, agent_type, or session_id to easily find and analyze specific agent executions.

Can I use my own API keys with Portkey?

Yes! Portkey uses your own API keys for the various LLM providers. It securely stores them, allowing you to easily manage and rotate keys without changing your code.

Resources

OpenAI Agents Docs

Official OpenAI Agents SDK documentation

Agent Examples

Example implementations for various use cases

Book a Demo

Get personalized guidance on implementing this integration

Ecosystem

LLM Integrations

Cloud Platforms

Guardrails

Plugins

Vector Databases

Agents

AI Apps

Libraries

Tracing Providers

MCP Clients

MCP Servers

​Introduction

OpenAI Agents SDK Official Documentation

​Installation & Setup

​Getting Started

​End-to-End Example

​Production Features

​1. Enhanced Observability

​2. Reliability - Keep Your Agents Running Smoothly

Automatic Retries

Request Timeouts

Conditional Routing

Fallbacks

Load Balancing

​3. Prompting in OpenAI Agents

Prompt Engineering Studio

​4. Guardrails for Safe Agents

Learn More About Guardrails

​5. User Tracking with Metadata

Learn More About Metadata

​6. Caching for Efficient Agents

​7. Model Interoperability

Supported Providers

​Set Up Enterprise Governance for OpenAI Agents

​Step 1: Implement Budget Controls & Rate Limits

​Setting Up Department-Specific Controls:

​Step 2: Define Model Access Rules

​Access Control Features:

​Example Configuration:

​Step 3: Implement Access Controls

​Step 4: Deploy & Monitor

​Enterprise Features Now Available

​Frequently Asked Questions

​Resources

OpenAI Agents Docs

Agent Examples

Book a Demo

Introduction

Installation & Setup

Getting Started

End-to-End Example

Production Features

1. Enhanced Observability

2. Reliability - Keep Your Agents Running Smoothly

3. Prompting in OpenAI Agents

4. Guardrails for Safe Agents

5. User Tracking with Metadata

6. Caching for Efficient Agents

7. Model Interoperability

Set Up Enterprise Governance for OpenAI Agents

Step 1: Implement Budget Controls & Rate Limits

Setting Up Department-Specific Controls:

Step 2: Define Model Access Rules

Access Control Features:

Example Configuration:

Step 3: Implement Access Controls

Step 4: Deploy & Monitor

Enterprise Features Now Available

Frequently Asked Questions

Resources