[KongchangAI]
· 2 min read· 1,115 words

How to Claim ChatGPT Pro's Hidden API Credits: A Four-Step Guide to Connecting DSH

How to Claim ChatGPT Pro's Hidden API Credits: A Four-Step Guide to Connecting DSH

ChatGPT Pro subscriptions include $100–500 in monthly API credit—claim it and connect DSH in four steps.

The article covers an often-overlooked hidden benefit of ChatGPT Pro subscriptions: $100–500 in monthly API credit depending on tier, usable only for API calls, billed separately from ChatGPT and Codex usage, and non-rolling. It walks through a four-step Bilibili tutorial: claim credit on the billing page, create and safeguard a key on the API platform, select the built-in OpenAI provider in DSH's model settings and paste the key, then verify connectivity in a new conversation. Eligibility requires a 7-day-old subscription, the same email on both sides, and owner status; trial and gifted subscriptions are ineligible. Keys are fully shown only once—leakage means paying for others. A 429 "Credit Balance Exhausted" error means monthly credit is used up.

Many ChatGPT Pro subscribers don't realize that their monthly subscription fee actually includes an API credit allowance—100 to 500 USD per month depending on the subscription tier. Unused credit doesn't roll over and is reset to zero at the end of each month. This credit can only be used for API calls and is completely separate from your usage in ChatGPT and Codex—think of it as two separate ledgers. A Bilibili creator has broken the entire process of claiming the credit and connecting it to DeepSeek Harness (DSH) into four steps—no relay service needed, no extra top-up required.

What Exactly Is This Credit?

This is an OpenAI benefit for Pro subscribers: the 100 USD tier grants 100 USD in API credit, the 200 USD tier grants 200 USD, and the 500 USD tier grants 500 USD, issued monthly. The key point is its scope—it's spent only on the API, calculated separately from what you consume on the ChatGPT web interface and in Codex, so they don't compete with each other.

200 tier grants 200

In other words, even if you don't use ChatGPT much day to day, this API credit is a separate budget—great for running scripts, connecting third-party tools, or doing experiments. Unused credit doesn't roll over, so it only makes sense to claim it every month.

API (Application Programming Interface) is a way for programs to exchange data in agreed-upon formats. OpenAI's API calls models via HTTP requests and bills by the number of input and output tokens, so it's naturally separate from the "unlimited monthly" model of web subscriptions. The API credit included with Pro subscriptions is essentially a USD balance on your API platform account, deducted per official pricing each time a call is made—consumption only occurs when an actual API request is sent. This is also why it doesn't affect usage in ChatGPT and Codex: the two use different billing channels—one is seat-based subscription, the other is pay-per-call.

Step 1: Claim the Credit

Open ChatGPT, go to Settings, open the Billing page, find the "API credit" item, and click to claim. The creator specifically notes that this step is where people most often get stuck—several hard requirements must all be met simultaneously:

  • Subscription must be at least 7 days old;
  • The ChatGPT account and the API platform must use the same email address;
  • You must be the owner of both accounts;
  • Trial subscriptions and gifted subscriptions are not eligible.

Select the API organization to receive the credit and click confirm to complete the transfer. In the first month, the amount is prorated by remaining days, so a smaller amount is normal.

And you must be the owner of both

Step 2: Create and Safeguard Your API Key

Open OpenAI's API platform, go to the API Keys page, and click "Create new secret key." Give it an easily recognizable name—for example, just call it DSH.

Here's a critical point: the key is only fully displayed once at creation time; afterward you can only see a masked version. The creator's advice is to copy it immediately and store it somewhere safe—never screenshot it and share it in a group chat. Anyone who gets the key will be spending your credit.

Copy and save it immediately

An API key is a high-entropy string that serves as the caller's identity credential on the API platform, typically placed in the Authorization field of the request header. For security reasons, the platform only retains its hash value, which cannot be reverse-engineered—so creation is the only chance to see it in full; afterward you can only regenerate it. Once a key is leaked, anyone holding it can impersonate your organization to make calls and consume credit. Platform-side usage limits and credit alerts are the first line of defense, so it's recommended to create separate keys for different purposes, making it easy to revoke one without affecting other applications.

Step 3: Connect the Key to DSH

Open DSH, go to Settings, click "Models," and select OpenAI from the provider list—it's a built-in option, so you don't need to enter an endpoint URL yourself. Paste in the key you just copied and click Save. After saving, the interface only shows a masked state—this is normal.

Then just pick a GPT-series model in the model selector. Button names may vary slightly across DSH versions—just look for the "Models" page in Settings and you'll find the corresponding entry point.

"Provider" refers to DSH's built-in model service adapter layer, which comes pre-configured with endpoint URLs, authentication methods, and parameter mappings. Users only need to select a provider and enter their key. Most third-party model aggregation tools work this way—the goal is to abstract away interface differences between vendors internally, making switching models as simple as changing a dropdown option. This also explains why you don't need to enter an endpoint URL yourself or deploy a relay service: DSH has already baked OpenAI's API conventions into its provider configuration, eliminating the need to manually construct base URLs or handle compatible formats.

Step 4: Verify Connectivity

Start a new conversation and send a "Hello"—if you get a normal reply, you're connected. If you encounter a 429 error with "Credit Balance Exhausted," it means the monthly credit has been used up. Wait for next month's issuance or top up yourself. If you don't want to spend extra, remember to turn off auto-recharge.

That means you're connected

429 is an HTTP status code indicating "too many requests"—i.e., rate limiting or insufficient quota—which is a different class of problem from 400 (invalid parameters) and 401 (invalid key). When the response body says Credit Balance Exhausted, it means authentication itself passed; the failure is due to balance, not permissions. So you should be troubleshooting credit, not the key. If auto-recharge is enabled, the system will directly charge your card to renew once the credit runs out, and your bill will increase without you noticing—which is why the practical advice is to turn off auto-recharge.

A Few Practical Tips

The value of this process is putting the "invisible" API budget in your subscription to use—especially for users already using DSH who don't want to pay extra. Three easily overlooked details are worth remembering: first, the 7-day subscription requirement triggers claiming eligibility, so new subscribers shouldn't rush; second, the email and owner identity must match on both sides—this is the most common sticking point; third, treat key security like a password—leaking it means paying for someone else.

It really is a waste not to claim free credit. I recommend making the claim a fixed monthly routine at the start of each month, treating it as part of your subscription management.

#ChatGPT Pro API credit#claim API credit#DeepSeek Harness#DSH setup#OpenAI API key#API credit eligibility
Share:

Related articles