AI Economics
AI Price Changes - June 2026 explains What changed in AI model pricing in June 2026, month-to-date through 2026-06-10: 215 price events across 30 providers in the ByteCosts ledger. This ByteCosts research article explains the cost mechanics behind the headline, turns the pattern into budgeting questions, and points readers toward calculators that can model the same issue with their own workload. Read it when you need a finance-readable explanation of AI Economics before choosing a model, cloud platform, subscription, or optimization path. The static HTML includes the summary, article body, tables, related tools, and citation before JavaScript runs.
Apply this concept - LLM API Pricing Index: Compare Model Costs by Provider →
In the ByteCosts committed pricing ledger as of 20260610, the June 2026 monthtodate slice contains 215 model price events across 30 providers. Every figure below traces to a dated ledger entry and its provider source. The tables show only prices and cuts that were current at the snapshot date.
Through 20260610, the ByteCosts ledger logged 215 June price events across 30 providers: 4 distinct standingrate cuts and 158 distinct firsttime prices. Some events appear under more than one provider domain or service tier, so the ledger contains 7 cut entries after those mirrored records are included. Of the firsttime prices, 150 remained the latest tracked rate for their model at the snapshot date.
A firsttime price means the rate was newly tracked by ByteCosts during June. It does not necessarily mean the provider launched the model during June. A standingrate cut means a previously tracked numeric rate fell and the newer row remained current at the snapshot date.
Mirrored records are deduplicated by model, price field, old value, and new value when reporting distinct changes. Corrections are excluded. The public June ledger export includes the event records and source URLs used for the summary.
In the ByteCosts committed pricing ledger as of 20260610, the June 2026 monthtodate slice contains 215 model price events across 30 providers. Every figure below traces to a dated ledger entry and its provider source. The tables show only prices and cuts that were current at the snapshot date.
Through 20260610, the ByteCosts ledger logged 215 June price events across 30 providers: 4 distinct standingrate cuts and 158 distinct firsttime prices. Some events appear under more than one provider domain or service tier, so the ledger contains 7 cut entries after those mirrored records are included. Of the firsttime prices, 150 remained the latest tracked rate for their model at the snapshot date.
A firsttime price means the rate was newly tracked by ByteCosts during June. It does not necessarily mean the provider launched the model during June. A standingrate cut means a previously tracked numeric rate fell and the newer row remained current at the snapshot date.
Mirrored records are deduplicated by model, price field, old value, and new value when reporting distinct changes. Corrections are excluded. The public June ledger export includes the event records and source URLs used for the summary.
| Model | Rate | Change | Source |
|---|---|---|---|
| MiniMaxM3 | cache read | $0.36 to $0.12 (66.7%) | MiniMax |
| MiniMaxM3 (Priority, 512k input) | cache read | $0.36 to $0.12 (66.7%) | MiniMax |
| MiniMax M3 | cache read | $0.12 to $0.06 (50%) | OpenCode Go |
| MiniMaxM3 (512k input) | cache read | $0.24 to $0.12 (50%) | MiniMax |
Newly tracked model prices this month, graded A or better in the ledger:
| Model | Rate | Latest price this month (per 1M tokens) | Source |
|---|---|---|---|
| MiniMax M3 Free | input | $0 | OpenCode Zen |
| DeepSeekV4Flash | cache read | $0.0028 | Deep Infra |
| deepseekv4flash | cache read | $0.0028 | DeepSeek |
| DeepSeekV4Pro | cache read | $0.003625 | Deep Infra |
| deepseekv4pro | cache read | $0.003625 | DeepSeek |
| Base Embeddings | embedding | $0.008 | Fireworks AI |
| GLM4.7FlashX | cache read | $0.01 | Z.AI |
| Base Embeddings | embedding | $0.016 | Fireworks AI |
A lower list price matters only after it is applied to the same workload. Keep input tokens, output tokens, cache behavior, retries, and request volume constant when comparing the old and new rates. Open the AI Provider Pricing Index to inspect the current sourcebacked row, then use Scenario Studio to see whether the change materially moves monthly cost or margin.
215 price events across 30 providers appear in the ByteCosts June 2026 monthtodate ledger slice. 4 distinct standingrate cuts and 158 distinct firsttime prices were logged. Firsttime prices mean newly tracked by ByteCosts; only standingrate cuts represent a drop in a previously tracked rate. The public export carries the event records and provider source URLs used for this digest.
After reading the research note, open the related calculator and replace the example assumptions with your own users, requests, tokens, seats, or platform usage.
The goal is to convert the article's cost pattern into a concrete monthly run-rate, per-user margin, or break-even point your team can discuss.
Yes. The prerendered HTML includes the article summary, direct answer, key sections, related tools, and citation block for crawlers and readers without JavaScript.
Yes. Use the related ByteCosts calculators to replace the article's example numbers with your own workload, usage, and pricing assumptions.
AI Price Changes - June 2026. ByteCosts. Updated 2026-06-10. https://bytecosts.com/blog/ai-price-changes-june-2026/