Skip to main content

RecordCatalogSync

POST 
/admin/v1/catalog/sync-state

Catalog sync freshness (fraser#7951), admin-key half.

Same wall, same shape as the writes above: the catalog-sync CronJob's only credential on a provisioned management plane is that plane's admin key, which cannot reach agentrouter.catalog.v1.CatalogService at all. Both routes delegate to the same catalog.Server, so there is one record and one set of merge rules whichever surface wrote it -- a hand-run with a session token and a nightly job with an admin key update the same row. Two records would be worse than none: each would look stale whenever the other ran.

Request​

Responses​

Success