FPFuturePedi

The archive

What changed

1 recorded movements, each dated the day it was observed. Nothing here is written by hand and nothing is backfilled — which is also why it starts empty and only grows.

11 event recorded
11 price move
00 model changes
00 status changes
price

chatgpt-plus price rose 25%20 → 25

How to read it

Anyone can tell you what Claude costs today.

What they cannot tell you is that it changed on a Thursday in June, that it was the third change this year, or that the provider has logged six incidents since March. Today's number is trivially copyable. A record of how it got there has to be written down as it happens — which is what these collectors do every day, whether or not anything moved.

An entry is only written once a change clears verification. When a collector cannot confirm a new value it keeps the last verified one and records nothing, so a bad scrape never becomes a fake price change sitting permanently in your history.

Prices

The day your budget assumption expired

Useful when you are renewing, forecasting next year's spend, or checking whether the quote a vendor gave you in March still holds. The date is the part you cannot reconstruct later.

2026-06-12 · price · chatgpt-plus rose 25% (20 → 25)
Models

The changes nobody emails you about

Output pricing, context windows and retirement dates move without a product announcement. A model you call in production can get a third more expensive per token, or quietly acquire a shutdown date, while its name and endpoint stay exactly the same.

2026-09-09 · model · claude-x output rose 33% (3 → 4)
Status

One outage is noise. Six is a procurement fact.

A provider's own status page tells you what is broken right now and forgets it afterwards. How often it broke over six months is a different question, and the one that matters when you are deciding what to depend on.

2026-09-10 · status · openai operational → outage