Marketplaces for API Key Users in the OpenAI Plugins Repository

The OpenAI Plugins repository integrates with multiple independent marketplaces—including Zoom, Zoom Gov, and Vercel—that issue API keys required for authentication, with the codebase automatically routing requests to the correct marketplace endpoint based on environment configuration.

The OpenAI Plugins repository hosts integrations that require API key authentication from various third-party platforms. When developers implement these plugins, they must obtain credentials from the specific marketplace for API key users that corresponds to their target platform, as each marketplace operates independently with distinct endpoints and credential requirements.

Supported Marketplaces for API Key Authentication

The repository contains dedicated integrations for several independent marketplaces. Each platform maintains its own credential issuance system and base URLs.

Zoom Standard Marketplace

The standard Zoom integration targets https://marketplace.zoom.us/ for SDK key generation. According to plugins/zoom/skills/video-sdk/web/references/web.md, developers obtain Zoom Video SDK keys and secrets from this marketplace to authenticate web, Android, iOS, and Unity plugins. The repository expects these credentials in environment variables named ZOOM_SDK_KEY and ZOOM_SDK_SECRET.

Zoom Gov Marketplace

For government-restricted environments, the repository supports https://marketplace.zoomgov.com/ as detailed in plugins/zoom/skills/video-sdk/web/examples/framework-integrations.md. This separate marketplace issues distinct SDK keys required for compliance with federal deployment standards. The codebase detects gov environments via the ZOOM_GOV environment flag.

Vercel Marketplace

The Vercel workflow plugin utilizes tokens from the Vercel Marketplace. As documented in plugins/vercel/skills/workflow/references/durable-agent-patterns.md, developers must generate Vercel-specific API tokens to enable deployment workflows and durable agent patterns.

Architecture of Marketplace Selection

The repository implements a configuration-driven architecture that automatically selects the appropriate marketplace endpoint based on the user's environment and credentials.

Configuration Files

Marketplace-specific configuration files—including environment-variables.md and full-guide.md—store endpoint URLs, credential names, and required scopes. These files define which environment variables map to which marketplace credentials.

Skill Implementation Pattern

Skill implementations import these configuration variables and instantiate the corresponding SDK or REST client. For Zoom integrations, the Video SDK client receives credentials directly from process.env variables.

Conditional Routing Logic

The codebase detects government contexts by checking the ZOOM_GOV flag. When this flag is set to 'true', the system switches the base URL from marketplace.zoom.us to marketplace.zoomgov.com before initializing the client.

Implementing API Key Authentication

The following patterns demonstrate how to load and use API keys from different marketplaces within the OpenAI Plugins repository.

Standard Zoom API key initialization from plugins/zoom/skills/video-sdk/web/SKILL.md:

const zoomSdkKey = process.env.ZOOM_SDK_KEY;
const zoomSdkSecret = process.env.ZOOM_SDK_SECRET;

// Initialise the Zoom Video SDK client
const client = ZoomVideoSDK.createClient({
  sdkKey: zoomSdkKey,
  sdkSecret: zoomSdkSecret,
  // Base URL automatically resolves to marketplace.zoom.us
});

Switching to Zoom Gov marketplace based on plugins/zoom/skills/video-sdk/web/examples/framework-integrations.md:

const isGov = process.env.ZOOM_GOV === 'true';
const baseUrl = isGov
  ? 'https://marketplace.zoomgov.com/'
  : 'https://marketplace.zoom.us/';

const client = ZoomVideoSDK.createClient({
  sdkKey: process.env.ZOOM_SDK_KEY,
  sdkSecret: process.env.ZOOM_SDK_SECRET,
  baseUrl,
});

Vercel API token usage from plugins/vercel/skills/workflow/references/durable-agent-patterns.md:

const vercelToken = process.env.VERCEL_API_TOKEN;
const vercel = new VercelClient({ token: vercelToken });

Summary

• The repository supports multiple marketplaces for API key users, including Zoom Standard, Zoom Gov, and Vercel.
• Each marketplace issues distinct credentials through independent URLs (marketplace.zoom.us, marketplace.zoomgov.com, and Vercel Marketplace).
• The codebase automatically routes requests to the correct endpoint by checking environment flags like ZOOM_GOV.
• Credentials are loaded from environment variables defined in marketplace-specific configuration files.
• Developers must obtain API keys from the specific marketplace that corresponds to their deployment target.

Frequently Asked Questions

What is the difference between Zoom and Zoom Gov marketplaces?

Zoom Gov (marketplace.zoomgov.com) operates as a separate, isolated marketplace for government-restricted environments with distinct SDK keys and compliance requirements. Standard Zoom (marketplace.zoom.us) serves commercial and general-purpose deployments. The repository detects which to use via the ZOOM_GOV environment variable.

How does the repository detect which marketplace to use?

The codebase checks configuration flags in environment variables. For Zoom integrations, it evaluates process.env.ZOOM_GOV === 'true' to determine whether to route requests to marketplace.zoomgov.com instead of the standard marketplace.zoom.us endpoint.

Can API key users access the OpenAI Plugin Marketplace directly?

Yes. The GitHub repository at https://github.com/openai/plugins serves as the central catalog where API key users can fetch plugin definitions and source code directly. This internal marketplace hosts the plugin manifests and skill implementations that reference external marketplaces for credentials.

Where are marketplace credentials stored in the codebase?

Credentials are not hardcoded in the repository. Instead, the codebase references environment variables—such as ZOOM_SDK_KEY, ZOOM_SDK_SECRET, and VERCEL_API_TOKEN—defined in marketplace-specific configuration files like plugins/zoom/skills/video-sdk/web/references/web.md and plugins/vercel/skills/workflow/references/durable-agent-patterns.md.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}