Search Knowledge

POST /knowledge-search

The annex 10 §3 pipeline over HTTP — its first route anywhere.

A POST with a body, not a GET with a similar_to parameter: half the pipeline behind a list filter is the second-way-to-search that knowledge_read refused to build, and the query is a sentence, not an identifier.

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.

Request body — KnowledgeSearchRequest

Field	Type		Notes
query	string	required	min length 1 max length 2000
knowledge_set	string | null	optional	—
limit	integer	optional	Default 8. min 1 max 25

Responses

Status	Description	Body
200	Successful Response	KnowledgeSearchView
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

The body shows the fields the schema always carries. Which combination is legal is a service rule the schema cannot express, so read the description above before copying this.

curl -X POST https://your-deployment.example.com/knowledge-search \
  -H "Authorization: Bearer $COBRE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "query": "string"
     }'

Response — KnowledgeSearchView

Field	Type		Notes
count	integer	required	—
direct	SearchHitView[]	required	—
related	RelatedHitView[]	required	—
budget	SearchBudgetView	required	—
skipped_kbs	string (uuid)[]	optional	Default [].