A model catalog used to have two states: available, at a price, or not available. This year it picked up a third: gated. OpenAI's Daybreak program - its gated cyber initiative, announced June 22 and fulfilled in August by GPT-5.6-Cyber at 12.50 / 75.00 per million tokens - is sold through Trusted Access for Cyber, an approval channel for verified defenders rather than a pay button. Anthropic shipped Claude Fable 5 on June 9 (10.00 / 50.00, 1M context, adaptive thinking) alongside Claude Mythos 5, available only in limited release through its Project Glasswing to a small circle of trusted partners. Two weeks after that launch, both models were suspended by US export controls applied June 12, and stayed off for 19 days until the controls lifted at the end of the month.
Model choice is becoming an access question as much as a price question, and access questions have an economics you already know: they are settled by allocation, not by price.
When price stops being the access mechanism
For decades, the model market had one gate: money. Pay the rate, get the tokens. The gated tiers move the gate off the price axis:
- Daybreak (OpenAI): GPT-5.6-Cyber at 12.50 / 75.00, with cached input at 1.25, sold through Trusted Access for Cyber. The price is public. The entitlement is not.
- Mythos 5 (Anthropic, Project Glasswing): the family's top tier at the 10.00 / 50.00 rate, in limited release to trusted partners and open-source maintainers. The family is public; the ceiling is not.
- The off-switch (June 12-30, 2026): US export controls applied to Fable 5 and Mythos 5; Anthropic suspended access for all users, global and gated alike, until the controls lifted on June 30. Not an outage, not a deprecation - a forced suspension, reversible in principle, with no SLA about when.
That is allocation doing the work price used to do. Providers now ration model access the way airports ration takeoff slots, utilities ration capacity, or exchanges ration market-maker seats: apply, qualify, wait, or lose.
The economics of an access gate
Providers replace price with allocation when they want a constraint price cannot enforce. Three show up in this year's tiers:
- Risk underwriting. Cyber capability is a category with a visible threat model. A public endpoint means a public threat surface. Gating lets the provider underwrite each customer, and the 12.50 / 75.00 rate is model-price plus risk-price in one number.
- Demand shaping. Allocation screens out workload patterns that degrade the service for everyone else - it is a quality filter price cannot do, because a price that screens only by willingness-to-pay invites the exact buyer you wanted to screen.
- Regulatory optionality. A gated tier is a valve. As the June off-switch showed, "the gated tier is off for 19 days" is a smaller event than "the model is off," which is much smaller than litigation. Allocation gives the valve a shape.
For buyers, the consequence is that access status is now an independent sales variable, next to price, latency, and quality. A catalog of prices is incomplete the same way a power rate is incomplete without a reliability class.
What gating changes in system design
- Every gated dependency is a single-vendor dependency in both directions. Price is a signal you can react to; status is a fact you can only receive. Any workload built on a gated tier needs a designed fallback to open tiers, maintained outside the approval process, because approvals take weeks and shipping does not wait weeks.
- Budget for unavailability as a normal state. The 19-day suspension is the data point. "This model may not exist today" belongs in the same risk register as "this model may be down," at higher severity and longer duration.
- Contracts should name the mechanism. A termination or force-majeure clause that covers scheduled deprecation but not a government-directed suspension has a drafting gap that one known incident sized for you.
Mappace tracks access state - open, gated, suspended, deprecating - as a first-class field on the model catalog and alerts when any of your routed targets change state, so the discovery path is a signal and not a 404.
What to do
- Add an access-state field (open / gated-apply / gated-enterprise / suspended) to your model catalog; every routing decision is now a function of it.
- For each workload that can run on a gated tier, pre-design and periodically test the open-tier fallback.
- Add "service unavailable by external directive" to your vendor-risk register now, while the 19-day example is fresh, and check your force-majeure wording against it.
- Price in the risk component of a gated rate: part of 12.50 is insurance you receive by being underwritten. The open alternative is cheaper per token and unterwritten.