Skip to main content

RegenerateCatalogRoutes

POST 
/admin/v1/catalog:regenerate-routes

Publish the catalogue to the data plane: one GLOBAL_ROUTES regeneration.

The counterpart to suppress_route_regen on the two upserts above. A batch caller suppresses per-write regeneration and calls this ONCE at the end, so ~700 entries cost one fan-out rather than ~700.

Deliberately takes NO caller-supplied scope. The underlying trigger must carry the "system" sentinel or the configurator narrows delivery to the caller's own customer, stranding every other workspace on the previous catalogue -- and the catalogue is global (ai_providers is keyed by name, ai_models is not customer-scoped). Server-side only, so a caller cannot get that wrong.

Request​

Responses​

Success