change_history

dev.aiseek/aiseek · Verify this server

How AiSeek's evidence record for one published change developed, and what AiSeek knew about it at an earlier moment. Always returns the change's receipts per claim, newest first (each names its parent receipt, so the revision chain reads from the list, with class, statuses and independence counts), and the change as it was when first published when the plan's window reaches that date. With `known_at` it also returns the change as known at that moment: whether readers could see it then, whether its headline wording changed later, and each claim's newest receipt written by then. Limits that are part of the answer: history is recorded from the day SeekTrace began, and before it a result says precision EXISTENCE_ONLY (whether a record existed, never what it said); old headline text is not kept, so `current` is today's version and the wording check says when it differs. `known_at` is limited by plan (Free 7 days back, Pro 30, Intelligence 90, Developer 180); asking further back is an error. A receipt records an assessment; it is not a certificate that a claim is true. Use it for what-did-we-know-then questions; use get_change for today's view. The id is the change id from latest_changes or search_changes. One call of the key's quota.