Knowledge synchronization

Knowledge bases provide policies, FAQs, product material, and documents as retrieved context. They do not decide tool authorization and must not store operational credentials.

Upsert a document

PUT /kb/{kb_id}/docs/{source_key}
Authorization: Bearer <client-token>
Content-Type: application/json

{
  "title": "Refund policy",
  "content": "Markdown or plain text",
  "metadata": { "tenant_id": "t_100", "source": "help-center" }
}

Derive source_key from a stable business identifier. Reusing a key replaces that document; deleting the same key removes it, which makes incremental synchronization and reconciliation deterministic.

GET /kb/{kb_id}/docs
DELETE /kb/{kb_id}/docs/{source_key}

A route retrieves knowledge only when explicitly configured. Retrieved text is model context, not current business truth; query orders, inventory, and account state through authoritative business tools.

Knowledge upsert schema