Vibeleaderboard
← All Intel
Intel / post

OpenAI flags sub2api resharing as fraud, keeps OSS sign-in supported

Source
x.com
Date
Tibo@thsottiaux
Thread · 2 parts

We've investigated a few messages about codex usage limits being different. That's not something we change without engaging the community and being transparent. What we did see is that when talking to affected users many were using sub2api. Converting a subscription into api traffic to then re-serve or share across many users is not something we support and this type of usage gets flagged by our fraud-prevention systems. You are completely fine if you use your subscription through Sign in With ChatGPT, either through the official clients or through one of the many OSS clients (Pi, OpenCode, ...) that support signing in with your account and using your included usage.

It's me again. I come bearing great news. First of all, we have hit 20M active users for Codex some time this week. Second of all, this is cause for celebration and during the day we will credit every Codex and ChatGPT Work user with a BANKED reset that you can use at your own leisure. And we will have some other good news later too! Now, on usage limits draining faster, while we're not seeing anything abnormal, we do take it incredibly seriously and there is an ongoing investigation. I will share if we do find anything and my below post is really a clarification on a specific pattern that we did see that I wanted to call out. Go do something amazing today.

Context

OpenAI's August 21, 2026 usage clarification distinguished personal subscription access through compatible clients from converting a subscription into an API service shared among multiple users. The post said the latter pattern triggered fraud-prevention systems, while signing into supported open-source clients with one's own account remained supported.

That distinction concerns how access is used and shared, rather than whether the client is open source. A follow-up also said investigation of faster usage depletion was continuing, so the sharing issue was not presented as a complete explanation for every user's complaint.

More from Tibo
Recommended reads
Comments

Checking sign-in…

Loading comments…