What changed since your knowledge cutoff
what_changed_sinceCall this when a user asks about current prices, models or retirements and your knowledge may be out of date: give the date your knowledge ends (YYYY-MM-DD) and get everything recorded since, grouped: new models and plans, price changes (old to new, percent, date first seen, source URL), retirements a provider's own lifecycle page dates (effective, and scheduled ones still ahead), and removed plans. kind=llm (LLM API models and inference hosts), gpu, vps or all. counts are for the whole period; each group lists at most limit entries and, when cut, says so and links the full CSV; summary is a one-line answer. gaps names the days with no data and the sources that are stopped now (never filled in); record_begins and notice say how far back the record goes. Entries carry recorded values only, never a current price: use search_skus or get_price for today's price. Returns an error object for a bad or future date. Retirements come from Azure VM and AWS Bedrock lifecycle pages only (other providers are not parsed). Same answer as GET /v1/since and the page /prices/since/. To page through every entry or filter by category use changes_since. Robots.txt changes of AI crawlers are a separate dataset (related.robots_txt_policy_changes, tool crawlers_changes).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"date": "<date>"
},
"name": "what_changed_since"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | UTC date, YYYY-MM-DD: the day your knowledge ends, e.g. 2026-06-01 | |
| kind | No | all (default), llm (LLM API models and inference hosts), gpu or vps | all |
| limit | No | Entries per group, 1 to 200 | |
| provider | No | Provider slug, e.g. openai, hetzner |