Get Knowledge Base Readiness

GET /knowledge-bases/{kb_id}/readiness

The checklist a feature screen renders: what works, what is missing, and the action that completes each step — with the conventional secret name as machine data, never as something a person is asked to know (D-5307).

viewer, like the rest of this file: it is a dashboard. What it reveals about credentials is existence at the organization level (“who pays”), never a name a viewer could act on — the actions themselves (PUT /secrets, the consolidation config) keep their admin floors.

Role floor

Requires viewer 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	KnowledgeBaseReadiness
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}/readiness \
  -H "Authorization: Bearer $COBRE_TOKEN"

Response — KnowledgeBaseReadiness

Field	Type		Notes
embeddings	FeatureReadiness	required	—
dreaming	FeatureReadiness	required	—
embedding_model	string | null	required, nullable	—
key_source	string | null	required, nullable	—
synthesis_model	string | null	required, nullable	—