What changed since a date
changes_sinceEverything recorded since a date, for a model whose knowledge ends at a cutoff: price changes, new items, removals and retirements, newest first, each with its UTC date, the previous good snapshot, the source URL and a permanent link to the item. counts are for the whole period (not just the page); gaps names the sources that are stopped now, with the day they stopped (never filled in; outages that recovered are not recorded); record_begins says how far back the record goes. summary=true returns the largest percent moves per category (at most 40 entries) in one answer, ordered by size of the move, not by price. Paging: pass next_cursor back as cursor. Entries carry recorded values only, never a current price. Returns an error object for a bad date or filter. Same data as GET /v1/changes-since. Use this one to page through every entry or to filter by category and kind (price_change, new_item, removed_or_stopped, retirement); for a first look at what changed since your cutoff, with counts, scope llm/gpu/vps and the gaps, call what_changed_since instead.
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": {
"since": "<since>"
},
"name": "changes_since"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | price_change, new_item, removed_or_stopped or retirement | |
| limit | No | Maximum entries per page, 1 to 1000 | |
| since | Yes | UTC date, YYYY-MM-DD, e.g. the day your knowledge ends | |
| cursor | No | next_cursor of the previous page | |
| summary | No | true = the largest moves per category in one answer | |
| category | No | vps, gpu, llm, inference or media | |
| provider | No | Provider slug, e.g. vultr, openai |