OpenAI Is Now Rationing Capability by Tier — Altman on GPT-6 Astra, Bloomberg

Sam Altman sat down with Bloomberg’s Ed Ludlow on 3 September to launch GPT-6 Astra, and the AGI framing in the headline is the least interesting thing he said. The interesting part is how the model is being released: not to everyone at a price, but in capability tiers, with the cyber-relevant capability held back.

The interview runs from roughly 26 minutes into the broadcast.

What is actually new

Asked what the guardrails on this release are, Altman does not describe a filter. He describes an access ladder:

“We will have different tiers of cyber access for this model for cyber in particular. Today, we’re rolling it out to trusted access.”

The framing around it is the standard capability-versus-risk trade, stated more plainly than usual:

“The challenge of our industry is that we have these models that are getting incredibly capable and incredibly useful… and then on the other hand, as these models get more capable, the risks that we have to mitigate also become more serious.”

And he concedes the schedule slipped for it:

“Obviously this model took us a little longer to release than we were hoping. I think it’ll be worth the wait, but we really wanted to spend the time on the safety and security alignment of this model.”

The context Bloomberg does not supply

The Bloomberg segment mentions “a string of security incidents” without specifics. The most consequential recent one is not OpenAI’s: between April and May 2026, attackers took over 20,225 Instagram accounts by asking Meta’s AI support assistant to add an attacker-controlled email to a victim’s account, and Meta’s own breach notification attributes it to a code path that failed to verify the email matched the account.

That is the environment Astra is being released into — an industry where an AI support surface was itself the vulnerability. Tiering cyber capability is a rational response to it, and it is also an admission that the safety properties of a frontier model are not yet good enough to hand the capability to everyone with a credit card.

The concession worth clipping

Ludlow raises Treasury Secretary Scott Bessent’s criticism at the G20 that the AI industry has failed to explain what any of this does for ordinary people. Altman does not deflect:

“I think the industry has done a terrible job of this on the whole. I think we have done a bad job ourselves, maybe better than some others, worse than some others.”

His diagnosis of the failure is more specific than the apology:

“You hear some people talk about, well, we’re going to give you a cure for cancer and that’s so great. So we’re going to, you know, take these risks and you’re going to have to have less power and autonomy. We want people to have more power and autonomy… I don’t think a cure for cancer is enough.”

That is a direct swipe at a framing common among his competitors, and it is worth noticing that it arrives in the same interview as a capability restriction. Both things are being said at once: users should have more autonomy, and this particular capability is going to trusted accounts first.

The pricing claim

On cost, Altman gives one specific number:

“Only a few weeks ago, we cut the price of Luna, our small model by 80%. And our goal is to have the best price performance at every level of intelligence, all the way along the curve.”

Plus a claim about Astra’s efficiency rather than its sticker price — “the amount of work you can get done with a relatively small amount of tokens.” That is the metric that matters for anyone running agents in production, and it is also the one that is hardest to verify from outside: token efficiency on your workload is not token efficiency on the benchmark. Measure it on your own tasks before believing it.

And the IPO line

Almost in passing, on whether the capital requirements push OpenAI toward public markets:

“If we do go public someday, which I assume we will, I plan to spend a lot of time reminding people who might want to buy or might not want to buy our stock that we are mission first and that we’re also extremely long-term oriented.”

“Which I assume we will” is about as close to on-the-record as this gets.

What to do with it

If you build on the API, find out which tier you are in before you design around a capability. The change here is that “what the model can do” is no longer a single answer. Test the specific capability you depend on from the account you will ship with, not from whichever account you prototyped with.

Treat token efficiency as a claim to measure, not a spec. Altman’s strongest argument for Astra is cost per task rather than capability, and cost per task is workload-dependent by definition.

Watch whether tiering spreads past cyber. Right now it is scoped to one capability class, described as a response to a specific risk. The mechanism generalises easily, and the first time it is applied to a capability that is merely commercially sensitive rather than dangerous will tell you what it is really for.