onchain_agent_get_changes

ai.satohub/onchain-agents · Verify this server

USE WHEN you keep a local copy of the directory and need only what moved since your last sync (machine-readable added / updated / removed), rather than re-fetching the whole catalog. NOT FOR a readable headline feed or one project's history (use onchain_agent_recent_changes instead), or the current state of one record (use onchain_agent_get_resource). RETURNS (json): what changed since a given date: additions, per-resource change events, and retirements. { since, until, window_days, counts:{added,changed,removed}, added:[...], changed:[{slug,name,url,events:[...]}], removed:[...], coverage:{...}, full_export }. COVERAGE (also stated in the response): `added` is exact. `updated` is a field-level diff of every catalog field between the snapshot on `baseline_date` and the live record — complete at daily resolution, so a quiet copy edit IS caught; store baseline_date as your cursor. `changed` is the richer event log (score moves, releases, verification) and explains WHY. `removed` is approximate. Mirror from added + updated + removed. Read-only. WITH NO `since` (and no detail: "full") the answer is compact, labelled rule "defaulted": exact counts for the default 14-day window and the newest rows of each lane (summary: true, shown, omitted, order, example_calls). It is a sample, not a sync. Pass `since` (any date) or detail: "full" for every row; a later `since` is a shorter window and a smaller answer. All free. Examples: - "what moved recently" -> {} (compact) · every row -> { detail: "full" } - "what's new this week" -> { since: "2026-08-23" } - "sync my copy" -> { since: <your last sync date> }