Get Consolidation Config

GET /knowledge-bases/{kb_id}/consolidation

What the maintenance pass will do to this base, and how often.

Readable at last. The document could be set at create time and never read back or changed: an operator asking “why did that pass do nothing” had a base whose enabled: false was invisible from every route in the API.

Role floor

Requires admin or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Parameters

Name	In	Type		Notes
kb_id	path	string (uuid)	required	—

Responses

Status	Description	Body
200	Successful Response	ConsolidationConfig
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

curl -X GET https://your-deployment.example.com/knowledge-bases/{kb_id}/consolidation \
  -H "Authorization: Bearer $COBRE_TOKEN"

Response — ConsolidationConfig

Field	Type		Notes
schema_version	integer	optional	Default 1. min 1
enabled	boolean	optional	Default false.
interval_seconds	integer	optional	Default 86400. min 60 max 31536000
model_ref	string | null	optional	—
stages	object	optional	—
promote_dry_run	boolean	optional	Default true.
thresholds	ConsolidationThresholds	optional	—
limits	ConsolidationLimits	optional	—