OpenAI is preparing to pay you in ChatGPT credits for using Stripe, HubSpot and other plugins

RUNTIMEWIRE INVESTIGATION — Scoop

Original reporting by RuntimeWire, based on reverse engineering.

Why it matters

OpenAI is tying rewards to completed plugin workflows, showing that third-party integrations are becoming a distribution and retention channel for ChatGPT Work and Codex.

Reporting record

When most people are sleeping, I'm putting the final touches on the RuntimeWire iOS and Android apps, and reverse engineering the latest ChatGPT for Windows update. And boy do we have a doozy.

OpenAI is preparing an incentive program that would add credits to ChatGPT workspaces when users install and successfully use selected third-party plugins, according to code shipping in the current ChatGPT Windows client.

The gated system names campaigns for Stripe, QuickBooks, HubSpot, Gusto, Dropbox and Canva. Each campaign identifier maps to a specific plugin, while the reward amount comes from OpenAI's servers rather than the desktop client. The implementation does not establish whether any of the six vendors are funding the promotion or participating in a marketing agreement.

The code appears in Windows client version 26.901.51231 and is controlled through an account flag named plugin_incentives_ui_enabled. That gate, combined with server-side eligibility and capacity checks, indicates OpenAI is testing or preparing the program rather than offering it broadly.

The feature is considerably more developed than a marketplace promotion. The client can retrieve an offer, enroll an eligible user, monitor whether the required plugin action succeeded and wait for OpenAI's billing system to confirm the award. The completion message reads: "{credits} added to your workspace."

OpenAI wants usage after installation

Installing a plugin alone would not earn the reward. The interface first instructs users to "Accept the offer and install the {pluginName} plugin," then requires them to "Use the {pluginName} plugin successfully in Codex or ChatGPT Work."

A separate callout on plugin detail pages says: "Try this plugin in Work or Codex to earn {credits} for your workspace."

That language gives OpenAI a measurable conversion event beyond an installation count. A qualifying user must invoke the plugin and complete an action that OpenAI recognizes as successful. The current client contains logic for pending verification, interrupted status checks, uncertain enrollment responses and billing confirmation.

The program also carries limits. A disclosure in the interface says credits go to the workspace and restricts each person to one reward across participating plugins and workspaces. Shared workspace limits also apply, and accepting an offer does not reserve credits.

OpenAI's backend can tell the client how many redemptions remain and when a claim or reward expires. The client expects records including the campaign, connector and plugin IDs; the credit award; the claim window; remaining redemptions; claim status; and timestamps covering enrollment, issuance and expiration.

Three endpoints handle the flow:

GET  /incentives/claims
GET  /incentives/{campaignId}
POST /incentives/{campaignId}/enroll

The implementation accounts for a user changing accounts or workspaces during a claim. It also checks for mismatched identities between the desktop client and the service running a task, reducing the chance that a plugin action on one account credits another workspace.

A more production-shaped rollout

The underlying incentive engine and six campaign identifiers were already present in Windows build 26.901.20858 on September 3rd. The September 6th build adds the user-facing language explaining how credits are earned, confirms that rewards can apply to both Codex and ChatGPT Work, and introduces the per-person and shared-workspace disclosures.

The earlier client described successful use only inside a Codex chat. The current version expands the qualifying action to ChatGPT Work, adds stronger identity checks and includes recovery states for offers that cannot immediately be confirmed. Those changes move the feature from a dormant campaign framework toward a system designed for users to encounter and complete.

OpenAI moved its app directory into a broader Plugin directory on July 9th. In OpenAI's plugin documentation, plugins are packages that can combine skills, connected apps and templates for repeatable workflows in ChatGPT and Codex. Installing one can trigger authentication for an underlying third-party service, while workspace administrators retain control over plugin availability and app permissions.

OpenAI has already made plugins central to its expansion of Codex beyond software development. In a June 2nd product announcement, OpenAI described role-specific workflows tied to business systems including HubSpot and Canva. The six incentive campaigns concentrate on widely used finance, sales, payroll, storage and design products, giving OpenAI several routes into day-to-day company operations.

Workspace credits have direct utility. OpenAI's Business billing documentation says shared credits can cover eligible Codex and other advanced usage after included allowances are exhausted. That lets OpenAI subsidize the first successful plugin workflow with a reward that can fund additional activity inside its own products.

The approach gives OpenAI a lever familiar to consumer marketplaces: pay for the behavior that matters rather than the download. Here, the desired behavior is a completed workflow that pulls an outside business system into ChatGPT Work or Codex. If the test reaches users, plugin vendors gain distribution, customers get subsidized usage and OpenAI gets evidence that its directory can produce repeat activity instead of rows of integrations that workers connect once and forget.